dbcve.org
BluespiceApplication · Hallowelt

CVE-2022-41814

MEDIUM · 5.4 CVSS v3.1 Published 2022-11-15
Fix available
A fix is available. Upgrade to 4.2.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Cross-site Scripting (XSS) vulnerability in BlueSpiceFoundation extension of BlueSpice allows user with regular account and edit permissions to inject arbitrary HTML into the history view of a wikipage.

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 confidence

Cross-site scripting (XSS) vulnerability in BlueSpiceFoundation allows authenticated users with standard edit permissions to inject arbitrary HTML/script into the history view of wikipages. This is a stored XSS where malicious content persists in the page history and executes when viewed by other users.

MitigationImplement proper output encoding and input sanitization for user-supplied content in the wiki page history view. BlueSpice should apply context-appropriate escaping (HTML, attribute, or JavaScript) before rendering user content in the history 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
BluespiceApplication
Affected:>= 4.1.0, < 4.2.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check BlueSpice installed version
    Locate the BlueSpice version file or check the admin dashboard for the installed version number. This is typically found in the software's about page, version info, or the composer.json / extension.json file in the BlueSpiceFoundation directory.
    Affected if Installed version is >= 4.1.0 and < 4.2.1
  2. Confirm authenticated user permissions
    Review user group permissions in BlueSpice to verify if standard authenticated users have 'edit' permissions enabled. Check the Special:ListGroupRights or user group configuration.
    Affected if Standard authenticated users have edit permissions and can access the wiki history feature
  3. Inspect page history for unexpected content
    View the source or HTML output of the Special:History page for one or more wikipages. Look for unescaped HTML tags, script elements, or event handlers in user contribution data.
    Affected if User-supplied content in page history renders as raw HTML or JavaScript instead of being escaped
  4. Check for stored malicious scripts
    Use the wiki's API or database query to retrieve recent page history entries. Examine the revision comments and content for patterns like <script>, javascript:, onload=, onerror=, or other HTML/script injections.
    Affected if Page history contains unsanitized HTML/script tags in user-generated fields

A system is affected if BlueSpice version is 4.1.0 through 4.2.0, standard users have edit access, and the page history view renders user content without proper HTML escaping.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.2.1 or later
Fixed in 4.2.1
Interim mitigation

Implement proper output encoding and input sanitization for user-supplied content in the wiki page history view. BlueSpice should apply context-appropriate escaping (HTML, attribute, or JavaScript) before rendering user content in the history interface.

Recommended fix Moderate confidence

BlueSpice 4.2.1

  1. Verify current Bluespice installation version by checking the wiki's version page or configuration
  2. Backup the entire Bluespice/MediaWiki installation and database before upgrading
  3. Consult BlueSpice upgrade documentation at en.wiki.bluespice.com for version-specific upgrade procedures
  4. Upgrade Bluespice from version 4.1.x to version 4.2.1 by following standard upgrade procedures (typically via composer update or the BlueSpice updater)
  5. After upgrading, verify the installation is running version 4.2.1 or higher
  6. Test the wiki history view functionality to confirm the fix is working properly
Caveat Review BlueSpice 4.2.1 release notes for any breaking changes between 4.1.x and 4.2.1; standard upgrade risks apply (backup recommended)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bluespice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41814 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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