CVE-2020-25158
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 · uneditedA reflected cross-site scripting (XSS) vulnerability in the B. Braun Melsungen AG SpaceCom Version L81/U61 and earlier, and the Data module compactplus Versions A10 and A11 allows remote attackers to inject arbitrary web script or HTML into various locations.
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 · moderate confidenceA reflected cross-site scripting (XSS) vulnerability exists in B. Braun Melsungen AG SpaceCom (version L81/U61 and earlier) and Data module compactplus (versions A10 and A11). The flaw allows remote attackers to inject arbitrary web script or HTML into various locations via reflected parameters, potentially enabling session hijacking, credential theft, or defacement of the medical device 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= a10= a11<= l81CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 if B. Braun SpaceCom is installedCheck system inventory or installed software list for 'SpaceCom' or 'B. Braun' medical device software componentsAffected if SpaceCom version is L81, U61, or any version earlier than L81/U61
-
Identify if B. Braun Data module compactplus is installedCheck system inventory or installed software list for 'Data module compactplus' or 'Compactplus' componentsAffected if Data module compactplus version is A10 or A11
-
Determine the exact SpaceCom version numberLocate the software version information in the device management console, system settings, or software inventoryAffected if Version number is L81, U61, or lower (earlier versions)
-
Determine the exact Data module compactplus versionLocate the software version information in the device management console, system settings, or software inventoryAffected if Version is exactly A10 or A11
-
Verify if the web interface is enabled and accessibleCheck device configuration for web server or HTTP service status; attempt to access the device web interface on typical management ports if authorizedAffected if Web interface is enabled and exposed on the network (required for XSS exploitation)
Your environment is affected if you have B. Braun SpaceCom version L81/U61 or earlier, or Data module compactplus version A10 or A11, and the web interface is enabled and network-accessible.
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 dataApply vendor-supplied patches or updates when available. Implement output encoding and input validation on all user-supplied parameters within the web interface. If patches are unavailable, consider network segmentation to limit exposure of these medical device interfaces.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25158 — 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-2020-25158 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