dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-40633

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Sylius is an Open Source eCommerce Framework on Symfony. A security vulnerability was discovered in the `/api/v2/shop/adjustments/{id}` endpoint, which retrieves order adjustments based on incremental integer IDs. The vulnerability allows an attacker to enumerate valid adjustment IDs and retrieve order tokens. Using these tokens, an attacker can access guest customer order details - sensitive guest customer information. The issue is fixed in versions: 1.12.19, 1.13.4 and above. The `/api/v2/shop/adjustments/{id}` will always return `404` status. Users are advised to upgrade. Users unable to upgrade may alter their config to mitigate this issue. Please see the linked GHSA for details.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The /api/v2/shop/adjustments/{id} endpoint in Sylius uses predictable incremental integer IDs for order adjustments. An unauthenticated attacker can enumerate valid adjustment IDs to retrieve order tokens, then use those tokens to access sensitive guest customer order details including personal information.

MitigationUpgrade to Sylius versions 1.12.19, 1.13.4 or higher, which disables the endpoint (returns 404). Alternatively, if upgrading is not possible, modify the API configuration to require authentication or restrict access to this endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Sylius installation version
    Check the installed Sylius version by inspecting the composer.json file in the project root, or run 'composer show sylius/sylius' to list the installed version
    Affected if The installed version is earlier than 1.12.19 or between 1.12.19 and 1.13.3 (non-inclusive)
  2. Confirm API endpoint is exposed
    Send a GET request to /api/v2/shop/adjustments/1 without any authentication headers
    Affected if The endpoint responds with HTTP 200 and returns JSON data (even if showing no adjustment or an error about the ID) rather than HTTP 404 or HTTP 401/403
  3. Test adjustment ID enumeration
    Send GET requests to /api/v2/shop/adjustments/{id} with incremental integer IDs (1, 2, 3, etc.) without authentication
    Affected if The endpoint returns order adjustment data or order tokens for multiple sequential IDs without requiring authentication
  4. Verify order token exposure
    Examine responses from the adjustment endpoint to see if they contain order tokens or links to order details
    Affected if Responses include 'order' references, order tokens, or redirect URLs that provide access to guest customer order information
  5. Check API security configuration
    Inspect the API routing configuration (typically in config/api_platform/resources.yaml or config/routes.yaml) and security settings (config/packages/security.yaml) to see if /api/v2/shop/adjustments is secured
    Affected if The endpoint route exists and does not require authentication (no security: { guard: } or access_control rules restricting it)
  6. Confirm guest order access
    If adjustment IDs return order tokens, use those tokens to access the guest order endpoint and retrieve customer PII
    Affected if The token can be used to access sensitive personal information from guest orders without authentication

A user is affected if the /api/v2/shop/adjustments endpoint is accessible without authentication and returns incrementing adjustment IDs that expose order tokens granting access to guest customer personal data

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Sylius versions 1.12.19, 1.13.4 or higher, which disables the endpoint (returns 404). Alternatively, if upgrading is not possible, modify the API configuration to require authentication or restrict access to this endpoint.

Recommended fix High confidence

Upgrade to Sylius 1.12.19+ or 1.13.4+

  1. Identify your current Sylius version by checking your composer.json or composer.lock file
  2. If using the 1.12.x branch, upgrade to version 1.12.19 or higher
  3. If using the 1.13.x branch, upgrade to version 1.13.4 or higher
  4. Run composer update sylius/sylius or composer require sylius/sylius:^1.12.19 (for 1.12.x) or ^1.13.4 (for 1.13.x)
  5. Deploy the updated application

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-40633 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-40633 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data