CVE-2012-1826
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 · unediteddotCMS 1.9 before 1.9.5.1 allows remote authenticated users to execute arbitrary Java code via a crafted (1) XSLT or (2) Velocity template.
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 confidencedotCMS versions 1.9 through 1.9.4 contain a code injection vulnerability allowing authenticated users to execute arbitrary Java code by submitting crafted XSLT or Velocity templates through the template management interface.
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= 1.9.2.1CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/C:P/I:P/A:P
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 dotCMS versionLocate the dotCMS installation and check the version file or access the admin dashboard System Information section. Common locations include the WAR file, the administration panel, or a version.properties file in the installation directory.Affected if The installed version is 1.9, 1.9.1, 1.9.2, 1.9.2.1, 1.9.3, or 1.9.4.
-
Confirm template management is accessibleLog into the dotCMS backend as an authenticated user and navigate to the Template Management interface (typically found under Content > Templates or the administration menu). Verify whether the interface allows creating or editing XSLT or Velocity templates.Affected if The template management interface is accessible to your user account and permits editing of template files.
-
Review recent template modificationsCheck the template management system for recently created or modified templates, particularly those containing XSLT or Velocity syntax. Look for templates with unfamiliar names, suspicious code patterns, or templates containing Java execution calls.Affected if Templates exist that were created or modified by unauthorized users or contain unexpected code that could execute Java commands.
-
Audit user access to template managementReview the list of users and roles with permissions to access the template management interface. Identify which accounts have write access to templates.Affected if Multiple user accounts or untrusted personnel have template editing permissions.
You are affected if your dotCMS installation is version 1.9 through 1.9.4 and the template management interface with XSLT/Velocity editing capabilities is accessible to users who should not have code execution capabilities.
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 dotCMS 1.9.5.1 or later. If immediate upgrade is not feasible, restrict administrative access to trusted personnel only and implement monitoring for unauthorized template modifications.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1826 — 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-2012-1826 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