CVE-2026-36458
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 · uneditedChestnutCMS v1.5.10 has a SQL injection vulnerability. The content parameter of the cms_content tag can be manipulated in the admin backend and injected into a SQL query when the template is rendered.
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 confidenceChestnutCMS v1.5.10 contains a SQL injection vulnerability in the cms_content tag's content parameter. Attackers with admin backend access can manipulate this parameter to inject arbitrary SQL queries that execute when templates are rendered.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 ChestnutCMS installationLook for ChestnutCMS files in the web root, typically in directories like /cms/, /chestnut/, or check for chestnut-specific Java/POM files in the application codebaseAffected if ChestnutCMS is present on the system
-
Check ChestnutCMS versionLocate version file or pom.xml in the CMS installation directory and compare the version number to v1.5.10Affected if The installed version is v1.5.10 or falls within the v1.5.x range
-
Verify cms_content tag usageSearch template files (.ftl, .vm, .jsp) for instances of 'cms_content' tag usage, particularly looking for the 'content' parameter being passedAffected if Templates contain cms_content tags with a dynamic content parameter
-
Identify admin backend accessCheck if admin panels or backend routes for ChestnutCMS are accessible or if user accounts with admin privileges exist in the systemAffected if Admin backend access is available or configurable
-
Confirm template rendering flowReview the application code to verify that the cms_content tag parameter flows into dynamic SQL query construction without parameterized queriesAffected if The content parameter from cms_content tag is used in raw SQL queries without prepared statements
You are affected if ChestnutCMS v1.5.10 is installed, the cms_content tag is used in templates, and admin backend access exists enabling manipulation of the content parameter during template rendering.
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 dataReplace dynamic SQL query construction with parameterized queries or prepared statements, and implement strict input validation on the content parameter before using it in database operations.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36458 — 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-36458 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