CVE-2015-7400
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 Lotus Mashups component in IBM Mashup Center 3.0.0.1 allows remote authenticated users to cause a denial of service (CPU consumption) via an XML external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) 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 confidenceIBM Mashup Center 3.0.0.1 Lotus Mashups component is vulnerable to XML External Entity (XXE) injection. Remote authenticated users can craft malicious XML containing external entity declarations combined with entity references, causing excessive CPU consumption and denial of service. The vulnerability stems from the XML parser processing untrusted external entity definitions.
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= 3.0.0.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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/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.
-
Confirm IBM Mashup Center versionLocate the Mashup Center installation and check the version information. This is typically found in the product's about page, installation directory metadata, or version file. Compare your installed version against the affected version 3.0.0.1.Affected if The installed version is exactly 3.0.0.1 (only this specific version is listed as affected).
-
Verify Lotus Mashups component is activeAccess the Mashup Center administration console or check the deployed web applications to confirm the Lotus Mashups component is enabled and running.Affected if The Lotus Mashups component is installed and active in the environment.
-
Inspect XML parser configuration for external entity processingExamine the XML parser configuration files or settings used by the Mashup Center. Look for configurations that control whether external entities are resolved during XML parsing. This may be in parser-specific configuration files or application server settings.Affected if The XML parser is configured to allow processing of external entity definitions (DOCTYPE declarations with external references).
-
Check for XML input handling in MashupsReview how the Mashup Center processes XML input in the Lotus Mashups component. Identify endpoints or functions that accept XML data from users.Affected if The Mashups component accepts and parses untrusted XML input without strict validation.
You are affected if you are running exactly version 3.0.0.1 of IBM Mashup Center with the Lotus Mashups component enabled and the XML parser configured to process external entities.
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 dataDisable XML external entity processing in the Mashup Center XML parser configuration, or implement strict input validation to reject XML containing DOCTYPE declarations with external entity references. Consider upgrading to a patched version if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7400 — 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-7400 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