CVE-2026-39229
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 · uneditedBolt CMS through 3.7.0 allows SQL Injection in the 'order' parameter of the content listing pages. An authenticated attacker with low-level privileges can exploit this through the OrderDirective component. This allows for the extraction of sensitive information
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 confidenceBolt CMS through version 3.7.0 contains a SQL injection vulnerability in the 'order' parameter of content listing pages. The vulnerability exists in the OrderDirective component and can be exploited by authenticated users with low-level privileges to inject malicious SQL queries and extract sensitive information from the database.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Confirm Bolt CMS installationIdentify if Bolt CMS is present on the system by checking for Bolt-specific files such as composer.json,bolt.yml, or the vendor/bolt directory in the web rootAffected if Bolt CMS is present and the installed version is 3.7.0 or lower
-
Determine Bolt CMS versionLocate the version file or composer.json in the Bolt CMS installation directory and extract the installed version numberAffected if The installed version is 3.7.0 or any version lower than 3.7.0
-
Locate OrderDirective componentSearch the Bolt CMS source code for the OrderDirective class or file that handles the 'order' parameter in content listing functionalityAffected if The OrderDirective component exists and processes the 'order' parameter without proper sanitization
-
Verify order parameter acceptanceAccess a content listing page endpoint (such as /admin/content/*) and inspect whether the 'order' parameter is accepted in the requestAffected if The content listing endpoint accepts an 'order' parameter that can be manipulated
-
Check low-privilege user accessReview the authentication and authorization configuration to determine if users with low-level privileges can access content listing pagesAffected if Low-privilege authenticated users have access to content listing pages with the vulnerable order parameter
A user is affected if Bolt CMS version 3.7.0 or lower is installed, the OrderDirective component handles the order parameter, and low-privilege authenticated users can access content listing pages with the order parameter.
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.
From vendor dataUpgrade to a patched version of Bolt CMS (3.7.1 or later). If unable to upgrade immediately, implement input validation and parameterized queries for the order parameter in the OrderDirective component to prevent SQL injection.
- 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-39229 — 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-39229 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