CVE-2025-57880
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 · uneditedImproper Encoding or Escaping of Output vulnerability in Hallo Welt! GmbH BlueSpice (Extension:BlueSpiceWhoIsOnline) allows Cross-Site Scripting (XSS). This issue affects BlueSpice: from 5 through 5.1.1.
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 confidenceThe BlueSpiceWhoIsOnline extension for BlueSpice/MediaWiki contains a Cross-Site Scripting (XSS) vulnerability due to improper encoding or escaping of output. The vulnerability allows attackers to inject malicious scripts through the 'who is online' functionality, which is rendered without proper sanitization. This affects versions 5 through 5.1.1 of BlueSpice.
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.0, < 5.1.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 BlueSpice versionLocate the version file or admin panel in your BlueSpice installation (typically in includes/Version.php or via Special:Version page). Compare the version number against the affected range: 5.0 through 5.1.1.Affected if The installed version is 5.0, 5.1.0, or 5.1.1.
-
Confirm BlueSpiceWhoIsOnline extension is activeNavigate to Special:Version in your MediaWiki/BlueSpice installation or check the extension directory for the WhoIsOnline extension files.Affected if The BlueSpiceWhoIsOnline extension is present and loaded.
-
Verify who-is-online widget is enabledCheck the extension configuration (usually in BlueSpiceWhoIsOnline.php or $wgBlueSpiceWhoIsOnlineSettings) to see if the who-is-online feature is set to enabled.Affected if The who-is-online feature is enabled and visible to users.
-
Inspect rendered output for user dataView a page where the who-is-online widget appears (often the sidebar or user dashboard). Examine the HTML source to see if usernames or user activity data are reflected without proper HTML encoding.Affected if User data from the who-is-online feature renders without escaping (visible as raw HTML tags in page source).
Your environment is affected if BlueSpice version is between 5.0 and 5.1.1 inclusive, the BlueSpiceWhoIsOnline extension is enabled, and the who-is-online feature is accessible to users.
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.
dbcve · scoped5.1.2
Apply the vendor-supplied patch or upgrade to BlueSpice version 5.1.2 or later, which contains the proper output encoding fixes. Until patched, restrict the who-is-online feature from untrusted users or implement Content Security Policy headers to mitigate XSS risks.
BlueSpice 5.1.2
- Upgrade BlueSpice to version 5.1.2 or later to resolve the XSS vulnerability in the BlueSpiceWhoIsOnline extension
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-57880 — 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-2025-57880 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