dbcve.org
BluespiceApplication · Hallowelt

CVE-2022-42001

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 BlueSpiceBookshelf extension of BlueSpice allows user with regular account and edit permissions to inject arbitrary HTML into the book navigation.

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 confidence

Stored XSS vulnerability in BlueSpiceBookshelf extension where authenticated users with standard edit permissions can inject arbitrary HTML/script into book navigation. The malicious payload is stored and executed when other users view the affected book pages.

MitigationImplement input validation and context-aware output encoding on all user-supplied content in the book navigation rendering pipeline to neutralize malicious scripts.

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. Determine installed Hallowelt Bluespice version
    Access the Special:Version page in your MediaWiki installation (index.php?title=Special:Version) or check the version via command line if you have shell access. Locate the 'BlueSpice' entry and note the version number displayed.
    Affected if The installed version is 4.1.0 through 4.2.0 (inclusive). Versions below 4.1.0 or at/above 4.2.1 are not affected.
  2. Verify BlueSpiceBookshelf extension is present
    On the Special:Version page, locate 'BlueSpiceBookshelf' in the extensions list. Alternatively, check your extensions directory for the BlueSpiceBookshelf folder and confirm it contains the extension.json or BlueSpiceBookshelf.php file.
    Affected if The BlueSpiceBookshelf extension is installed and listed on Special:Version.
  3. Confirm book navigation functionality is in use
    Navigate to the Bookshelf manager (usually at Special:BookManager or look for the Bookshelf portal in the sidebar). Check if any books have been created with navigation enabled. Look for entries in the 'My Books' or 'Books' namespace.
    Affected if One or more books exist with navigation enabled in your BlueSpice installation.
  4. Verify standard edit permissions exist
    Go to Special:ListGroupRights or check your LocalSettings.php for user group permissions. Confirm that authenticated users (such as those in the 'user' group) have the 'edit' right granted.
    Affected if Standard authenticated users (not just administrators) have edit permissions enabled.

Your environment is affected if Bluespice version is 4.1.0 through 4.2.0, the BlueSpiceBookshelf extension is installed, books with navigation exist, and standard users have edit permissions.

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 input validation and context-aware output encoding on all user-supplied content in the book navigation rendering pipeline to neutralize malicious scripts.

Recommended fix High confidence

BlueSpice 4.2.1 or later

  1. Backup your BlueSpice installation and database before proceeding with any upgrade
  2. Verify your current BlueSpice version is within the affected range (>= 4.1.0 and < 4.2.1)
  3. Upgrade BlueSpice to version 4.2.1 or later following the standard upgrade procedure for your deployment method
  4. After upgrade, clear any caches to ensure the new version is fully loaded
  5. Verify the upgrade was successful by checking the BlueSpice version in the administration panel
  6. Test that the BlueSpiceBookshelf extension no longer allows arbitrary HTML injection in book navigation

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

Fix this in Bluespice Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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