CVE-2015-0931
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 · uneditedEktron Content Management System (CMS) 8.5 and 8.7 before 8.7sp2 and 9.0 before sp1, when the Saxon XSLT parser is used, allows remote attackers to execute arbitrary code via a crafted XSLT document, related to a "resource injection" issue.
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 confidenceEktron CMS contains a resource injection vulnerability in the Saxon XSLT parser that allows remote attackers to execute arbitrary code by submitting crafted XSLT documents. The vulnerability affects versions 8.5, 8.7 before SP2, and 9.0 before SP1.
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= 8.5.0= 8.7.0= 8.9.0CVSS 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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/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 Ektron CMS installationLocate the Ektron CMS installation directory on the web server; check for the presence of ektron.*.dll files or the CMS folder structure typically found in the web rootAffected if Ektron CMS is present on the server
-
Determine installed Ektron CMS versionOpen the web.config file in the CMS root directory and locate the version string in the assembly or version configuration section, or check the Ektron assembly DLL properties for the version numberAffected if The version number matches 8.5.0, 8.7.0, or 9.0 (or falls between 8.7.0 and 8.7 SP2, or between 9.0 and 9.0 SP1)
-
Verify Saxon XSLT parser is enabledSearch the web.config file for entries containing 'Saxon', 'xslt', or 'XslTransform' to determine if the Saxon processor is configured as the XSLT engineAffected if The Saxon XSLT parser is explicitly configured or referenced in the configuration files
-
Check for Saxon library presenceExamine the bin or libraries directory for Saxon*.dll or Saxon9*.dll assemblies that indicate the Saxon XSLT processor is deployedAffected if Saxon DLL files are present in the application bin or library folders
A user is affected if Ektron CMS versions 8.5.0, 8.7.0, or 9.0 (or any version before 8.7 SP2 or 9.0 SP1) are installed AND the Saxon XSLT parser is enabled in the configuration.
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 Ektron CMS 8.7sp2 or 9.0sp1 and later versions to resolve the vulnerability; alternatively, disable or restrict the Saxon XSLT parser configuration if immediate upgrade is not feasible.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0931 — 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-2015-0931 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