LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32720: List of order ids, number, items total and token value exposed for unauthorized uses via new API

Sylius is an Open Source eCommerce platform on top of Symfony. In versions of Sylius prior to 1.9.5 and 1.10.0-RC.1, part of the details (order ID, order number, items total, and token value) of all placed orders were exposed to unauthorized users. If exploited properly, a few additional information like the number of items in the cart and the date of the shipping may be fetched as well. This data seems to not be crucial nor is personal data, however, could be used for sociotechnical attacks or may expose a few details about shop condition to the third parties. The data possible to aggregate are the number of processed orders or their value in the moment of time. The problem has been patched at Sylius 1.9.5 and 1.10.0-RC.1. There are a few workarounds for the vulnerability. The first possible solution is to hide the problematic endpoints behind the firewall from not logged in users. This would put only the order list under the firewall and allow only authorized users to access it. Once a user is authorized, it will have access to theirs orders only. The second possible solution is to decorate the `\Sylius\Bundle\ApiBundle\Doctrine\QueryCollectionExtension\OrdersByLoggedInUserExtension` and throw `Symfony\Component\Security\Core\Exception\AccessDeniedException` if the class is executed for unauthorized user.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Certain Sylius eCommerce versions exposed limited order information to unauthenticated users through a new API. The exposed data was not described as personal data, but could reveal order volume, order value at a point in time, cart item counts, or shipping timing details useful for social engineering or competitive intelligence.

Executive priority

Treat as a moderate-priority eCommerce data exposure issue. It is unlikely to be an emergency absent other evidence, but public shops should patch or restrict access promptly because leaked order metadata can harm customer trust and support targeted fraud.

Technical view

CVE-2021-32720 is a CWE-200 information exposure issue in Sylius versions >=1.9.0,<1.9.5 and >=1.10.0-ALPHA.1,<=1.10.0-BETA.1. Unauthorized users could access order ID, order number, items total, and token value. Sylius patched it in 1.9.5 and 1.10.0-RC.1.

Likely exposure

Exposure is most likely for Sylius shops running the affected 1.9 or 1.10 prerelease ranges with the vulnerable API reachable by unauthenticated users.

Exploitation context

The bundle reports no KEV listing and no cited evidence of active exploitation. Impact is confidentiality only: order metadata leakage that could support social engineering or business-intelligence collection, not direct payment or account compromise based on available sources.

Researcher notes

The source bundle does not name exact endpoint paths or provide evidence of exploitation. Avoid expanding impact beyond order metadata listed in the advisory. Focus validation on authorization behavior around order collection access and whether deployed versions include the Sylius fix.

Mitigation direction

  • Upgrade affected Sylius deployments to 1.9.5, 1.10.0-RC.1, or a later fixed release.
  • Restrict the problematic order API endpoints behind authentication for unauthenticated users.
  • Ensure authenticated users can access only their own orders.
  • If upgrading is delayed, apply the documented extension decoration and deny unauthorized execution.
  • Review Sylius vendor guidance before relying on compensating controls.

Validation and detection

  • Inventory Sylius versions and flag deployments in the affected 1.9 and 1.10 prerelease ranges.
  • Confirm unauthenticated users cannot retrieve order lists or order metadata through the API.
  • Review firewall and route configuration protecting order-related API access.
  • Check logs for unusual unauthenticated requests to order-related API routes.
  • Verify regression coverage for unauthorized order API access.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32720 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2021-32720Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SyliusSylius>= 1.9.0, < 1.9.5, >= 1.10.0-ALPHA.1, <= 1.10.0-BETA.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.