CVE-2014-7296
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 · uneditedThe default configuration in the accessibility engine in SpagoBI 5.0.0 does not set FEATURE_SECURE_PROCESSING, which allows remote authenticated users to execute arbitrary Java code via a crafted XSL document.
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 confidenceSpagoBI 5.0.0's accessibility engine contains an XML/XSL processor that does not have FEATURE_SECURE_PROCESSING enabled by default. This allows authenticated remote users to submit crafted XSL documents containing malicious XSLT instructions that can execute arbitrary Java code on the server through the underlying XSL transformer.
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= 5.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 SpagoBI installation and versionLocate the SpagoBI installation directory and check the version file (typically VERSION.txt, about.html, or manifest files in the webapp). SpagoBI is typically deployed as a Java web application under appservers like Tomcat or JBoss.Affected if The installed version is exactly 5.0.0 (no patches applied)
-
Locate the accessibility engine componentNavigate to the SpagoBI web application directory and find the accessibility engine module. This is typically in a path containing 'accessibility' or 'spagobi-accessibility' within the WEB-INF or lib directories.Affected if The accessibility engine component exists and is deployed on the server
-
Check if accessibility feature is enabledExamine the SpagoBI configuration files (spagobi.xml, spagobi_beans.xml, or web.xml) for the accessibility engine configuration. Look for bean definitions or servlet mappings related to accessibility services.Affected if The accessibility feature is enabled in the configuration (present and active)
-
Inspect the XSL transformer configurationWithin the accessibility engine source or compiled classes, locate the XSL processor/transformer initialization code. Look for TransformerFactory or similar XML processing code that handles XSL/XSLT submissions.Affected if The code creates a TransformerFactory without explicitly setting FEATURE_SECURE_PROCESSING to true
-
Verify FEATURE_SECURE_PROCESSING settingSearch the accessibility engine code for 'FEATURE_SECURE_PROCESSING' or 'setFeature' calls related to the XSL TransformerFactory. Check if the security feature is explicitly enabled or if the default (disabled) is being used.Affected if FEATURE_SECURE_PROCESSING is not explicitly set to true, or the code relies on the default (insecure) setting
A user is affected if they are running SpagoBI version 5.0.0 with the accessibility engine enabled and the XSL transformer does not have FEATURE_SECURE_PROCESSING explicitly set to true.
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 dataEnable FEATURE_SECURE_PROCESSING on the XSL TransformerFactory in the accessibility engine code to restrict XSLT execution to a safe sandboxed mode, preventing arbitrary code execution.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7296 — 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-2014-7296 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