dbcve.org
BluespiceApplication · Hallowelt

CVE-2022-41789

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 BlueSpiceDiscovery skin of BlueSpice allows logged in user with edit permissions to inject arbitrary HTML into the default page header 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

A stored cross-site scripting (XSS) vulnerability exists in the BlueSpiceDiscovery skin of BlueSpice. Authenticated users with edit permissions can inject arbitrary HTML (including script tags) into the default page header of a wikipage, which will be executed when other users view the affected page.

MitigationImplement proper input sanitization and output encoding for the page header field in the BlueSpiceDiscovery skin. The fix should validate and sanitize any user-supplied HTML before rendering it, using a proper HTML sanitization library.

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. Identify installed BlueSpice version
    Access the BlueSpice admin panel or check the version file in the installation directory. Common locations include the Special:Version page in MediaWiki or a version.php file in the includes directory.
    Affected if The installed version is >= 4.1.0 and < 4.2.1
  2. Confirm BlueSpiceDiscovery skin is active
    Navigate to the skin settings in BlueSpice admin panel or check the $wgDefaultSkin configuration in LocalSettings.php to see if 'bluespicediscovery' is set as the default skin.
    Affected if The BlueSpiceDiscovery skin is enabled or set as the default skin
  3. Check for page header content in wikitext
    Inspect the source of affected wikipages by viewing the page in edit mode or checking the page content for any injected HTML in what would be rendered as the page header. Look for <script> tags or other JavaScript in the header fields.
    Affected if Arbitrary HTML or script tags are present in page header fields that are not properly sanitized
  4. Verify user edit permissions
    Review the user rights and permissions configuration to determine which authenticated users have edit permissions on the wiki.
    Affected if Authenticated users with edit permissions exist in the system

A user is affected if BlueSpice version is between 4.1.0 and 4.2.1 (exclusive), the BlueSpiceDiscovery skin is active, and the page header field accepts unsanitized HTML input that can execute JavaScript.

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 input sanitization and output encoding for the page header field in the BlueSpiceDiscovery skin. The fix should validate and sanitize any user-supplied HTML before rendering it, using a proper HTML sanitization library.

Recommended fix High confidence

4.2.1

  1. Back up your current BlueSpice installation and database before proceeding with the upgrade
  2. Upgrade BlueSpice to version 4.2.1 or later
  3. Verify the upgrade was successful by logging in and testing the BlueSpiceDiscovery skin functionality
  4. Confirm the XSS vulnerability is resolved by testing that arbitrary HTML cannot be injected into the default page header

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41789 — 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-41789 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