How to use this reference
Editorial lesson: define operation permissions independently from object ownership, and reconcile provider outcomes with local fulfillment state. The advisory recommends rejecting disallowed customer-context operations before effects. Maintainer release notes corroborate remediation in 2.1.16 and 2.2.9.
Before reading
- Basic application state machines, authorization and database transaction concepts
Context and limits
- Affected ranges are listed as 2.0.0 through versions before 2.1.16, and 2.2.0 through versions before 2.2.9.
- Impact is conditional on an enabled production API and a gateway exposing the relevant financial operations. The advisory explicitly excludes a plain default installation lacking that gateway.
- The maintainer describes financial-state inconsistency and consequent merchant-loss risk, not a documented production loss. This review does not independently verify those outcomes.
- TheMilek published the advisory; acirtautas is credited as finder. The reviewed advisory displays no known CVE; no identifier is inferred from secondary indexing.
- Official GitHub release metadata (release-21-metadata and release-22-metadata) records v2.1.16 published September 2, 2026 at 14:03:30 UTC and v2.2.9 at 14:03:48 UTC; both release bodies link GHSA-2rv4-pjmm-7fxf. These are software patch-release dates, not an educational-resource edition date; dates.version_released remains null.
Sources
- Shop API accepts arbitrary PaymentRequest actions, allowing a customer-triggered refundSylius · reviewed 2026-10-03
- Sylius v2.1.16 security releaseSylius · reviewed 2026-10-03
- Sylius v2.2.9 security releaseSylius · reviewed 2026-10-03
- Sylius v2.1.16 official GitHub release metadataSylius · reviewed 2026-10-06
- Sylius v2.2.9 official GitHub release metadataSylius · reviewed 2026-10-06
Record reviewed 2026-10-06. Snapshot af2809c308fc. Open the complete JSON contract.