Quick answers
- Is CVE-2026-53639 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53639 being exploited in the wild.
- How severe is CVE-2026-53639?
- Medium severity, with a CVSS score of 4, published 8 September 2026.
- Which products and versions are affected?
- sylius/sylius (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=2.0.18; Sylius >= 2.0.0, < 2.0.18.
- Is there a fix for CVE-2026-53639?
- Yes. sylius/sylius (Packagist): upgrade to 2.0.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53639 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53639?
- Check whether you run sylius/sylius (Packagist) or Sylius at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- sylius/sylius (Packagist): upgrade to 2.0.18 or later
composer require sylius/sylius:^2.0.18
Technical details
An Insecure Direct Object Reference (IDOR) exists in the GET, PUT, and POST endpoints for payment requests in Sylius. The application fails to verify if the authenticated user or guest session owns the order associated with a payment request hash or token. By obtaining a payment request UUID, an attacker can retrieve the underlying order's tokenValue, granting access to full order details including customer PII. Additionally, attackers can modify 'target_path' and 'after_path' fields to redirect users to malicious URLs during the payment flow. The issue is fixed in versions 2.0.18, 2.1.15, and 2.2.6.
Affected products
- Sylius Sylius/Sylius >= 2.0.0, < 2.0.18
- Sylius Sylius/Sylius >= 2.1.0, < 2.1.15
- Sylius Sylius/Sylius >= 2.2.0, < 2.2.6
Identifiers
- CVE-2026-53639
- GHSA-mr9r-h354-966r
Timeline
- 2026-06-02: disclosed: Initial publication date
- 2026-07-09: advisory: Last updated date