dbcve.org
BluespiceApplication · Hallowelt

CVE-2022-42000

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 BlueSpiceSocialProfile extension of BlueSpice allows user with comment permissions to inject arbitrary HTML into the comment section 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

Stored XSS vulnerability in BlueSpiceSocialProfile extension allows authenticated users with comment permissions to inject arbitrary HTML/JavaScript into wiki page comments. When other users view these comments, the malicious payload executes in their browsers, potentially enabling session hijacking, credential theft, or defacement.

MitigationImplement proper output encoding/HTML sanitization on all user-submitted comment content before rendering, using a vetted HTML sanitization library and following OWASP XSS prevention guidelines.

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 BlueSpice installation
    Check for BlueSpice installation by looking for the /bluespice directory in your web root, or check the MediaWiki Special:Version page for BlueSpice components
    Affected if BlueSpice is not installed
  2. Verify BlueSpice version
    Navigate to Special:Version in your wiki or check the BlueSpice version file (typically in includes/BlueSpiceVersion.php) and compare to the affected range: >= 4.1.0 and < 4.2.1
    Affected if Version is 4.1.0 through 4.2.0
  3. Confirm BlueSpiceSocialProfile extension is active
    Check your LocalSettings.php for the line 'enableSemantics()' and look for inclusion of the BlueSpiceSocialProfile extension, or check Special:Version for 'BlueSpiceSocialProfile'
    Affected if BlueSpiceSocialProfile extension is loaded and active
  4. Check if user comment permissions are granted
    Navigate to Special:WikiAdminUserRights or check $wgGroupPermissions in LocalSettings.php to determine if authenticated users have the 'social-profile-add-comment' or 'edit' right
    Affected if Authenticated users can post comments

You are affected if you are running Hallowelt Bluespice version 4.1.0 through 4.2.0 with the BlueSpiceSocialProfile extension enabled and users have permission to post comments.

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/HTML sanitization on all user-submitted comment content before rendering, using a vetted HTML sanitization library and following OWASP XSS prevention guidelines.

Recommended fix High confidence

BlueSpice 4.2.1 or later

  1. 1. Backup your current BlueSpice installation and database before proceeding with any upgrade.
  2. 2. Review the official BlueSpice upgrade documentation at en.wiki.bluespice.com for your specific version upgrade path.
  3. 3. Download BlueSpice version 4.2.1 or later from the official BlueSpice distribution channels.
  4. 4. Apply the upgrade following the standard BlueSpice upgrade procedure (typically via the web installer or composer update).
  5. 5. Verify that the BlueSpiceSocialProfile extension has been updated as part of the upgrade.
  6. 6. Test the comment functionality in the BlueSpiceSocialProfile to confirm XSS filtering is working properly.
Caveat No specific breaking changes documented for this security update; standard upgrade precautions apply

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

Fix this in Bluespice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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