CVE-2026-31825
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 · uneditedSylius is an Open Source eCommerce Framework on Symfony. Sylius API filters ProductPriceOrderFilter and TranslationOrderNameAndLocaleFilter pass user-supplied order direction values directly to Doctrine's orderBy() without validation. An attacker can inject arbitrary DQL. The issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.23, 1.13.15, 1.14.18, 2.0.16, 2.1.12, 2.2.3 and above.
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 confidenceSylius API filters (ProductPriceOrderFilter and TranslationOrderNameAndLocaleFilter) accept user-supplied order direction parameters and pass them directly to Doctrine's orderBy() method without validating that the input is a legitimate order direction value (ASC/DESC). This allows an attacker to inject arbitrary DQL (Doctrine Query Language) by supplying malicious values in the order parameter.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.9.12>= 1.10.0, < 1.10.16>= 1.11.0, < 1.11.17>= 1.12.0, < 1.12.23>= 1.13.0, < 1.13.15>= 1.14.0, < 1.14.18>= 2.0.0, < 2.0.16>= 2.1.0, < 2.1.12>= 2.2.0, < 2.2.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Sylius versionLocate the Sylius version file (typically composer.lock or a version class in the Sylius bundle), or run 'composer show sylius/sylius' to display installed version informationAffected if The installed version falls within any of the following ranges: < 1.9.12, >= 1.10.0 < 1.10.16, >= 1.11.0 < 1.11.17, >= 1.12.0 < 1.12.23, >= 1.13.0 < 1.13.15, >= 1.14.0 < 1.14.18, >= 2.0.0 < 2.0.16, >= 2.1.0 < 2.1.12, or >= 2.2.0 < 2.2.3
-
Locate vulnerable filter classesSearch the codebase for ProductPriceOrderFilter and TranslationOrderNameAndLocaleFilter class files, typically found in src/Sylius/Bundle/ApiBundle/Filter or similar directory under the ApiBundleAffected if These filter classes exist in the codebase and are being used by API controllers
-
Verify order parameter handling lacks validationExamine the filter class implementation to see if the order parameter (passed via request query string) is validated against allowed values (ASC/DESC) before being passed to Doctrine's orderBy() methodAffected if The code passes the order parameter directly to orderBy() without checking if the value is exactly 'ASC' or 'DESC' (case-insensitive validation may also be missing)
-
Check if API endpoints using these filters are exposedReview API routing configuration (routes.yaml or annotations) to identify endpoints that utilize ProductPriceOrderFilter or TranslationOrderNameAndLocaleFilterAffected if API endpoints that accept an 'order' query parameter are publicly accessible without additional authorization safeguards
You are affected if your Sylius installation version is within the vulnerable ranges AND the API endpoints using these filters are accessible, AND the code lacks validation ensuring order parameter values are strictly 'ASC' or 'DESC' before passing to Doctrine's orderBy().
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.9.121.10.161.11.17
Upgrade to a fixed version (1.9.12+, 1.10.16+, 1.11.17+, 1.12.23+, 1.13.15+, 1.14.18+, 2.0.16+, 2.1.12+, 2.2.3+) or implement strict input validation ensuring order direction values are only 'ASC' or 'DESC' before passing to orderBy().
Upgrade to one of: 1.9.12, 1.10.16, 1.11.17, 1.12.23, 1.13.15, 1.14.18, 2.0.16, 2.1.12, or 2.2.3+ depending on your current major version
- Identify current Sylius version by checking composer.json or bin/console sylius:version
- Backup the entire codebase and database before proceeding with any changes
- Update composer.json to require the fixed version: for 1.12.x use ^1.12.23, for 1.11.x use ^1.11.17, for 1.10.x use ^1.10.16, or for 1.9.x use ^1.9.12
- Run 'composer update sylius/sylius --with-all-dependencies' to install the patched version
- Run database migrations if any are required: 'bin/console doctrine:migrations:migrate'
- Clear the application cache: 'bin/console cache:clear'
- Test the API endpoints that use ProductPriceOrderFilter and TranslationOrderNameAndLocaleFilter to confirm the fix works and no regressions exist
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31825 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-31825 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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