dbcve.org
BluespiceApplication · Hallowelt

CVE-2022-2510

MEDIUM · 6.1 CVSS v3.1 Published 2022-07-22
Fix available
A fix is available. Upgrade to 3.2.9 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 "Extension:ExtendedSearch" of Hallo Welt! GmbH BlueSpice allows attacker to inject arbitrary HTML (XSS) on page "Special:SearchCenter", using the search term in the URL.

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

Reflected XSS vulnerability in BlueSpice's ExtendedSearch extension allows attackers to inject arbitrary HTML/script via the search term parameter on the Special:SearchCenter page. The search term from the URL is rendered without proper output encoding.

MitigationImplement proper output encoding/escaping on the search term before rendering it on the Special:SearchCenter page, and validate/sanitize search input.

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:>= 3.0, < 3.2.9= 4.1.0

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 product installation
    Check if Hallowelt Bluespice is installed by reviewing your web application stack or wiki installation directory. Look for BlueSpice-specific files or check the wiki's version information page (usually at /wiki/Version or in the admin dashboard).
    Affected if The product is Hallowelt Bluespice and the installed version falls within >= 3.0, < 3.2.9 or equals 4.1.0
  2. Verify ExtendedSearch extension is enabled
    Check if the ExtendedSearch extension is installed and active. This can typically be found in the wiki's LocalSettings.php file (look for 'wfLoadExtension' or 'enableSemantics' calls related to ExtendedSearch) or through the wiki's Special:Version page.
    Affected if ExtendedSearch extension is enabled and loaded in the BlueSpice installation
  3. Confirm Special:SearchCenter page exists and is accessible
    Access the Special:SearchCenter page in the wiki (typically at /wiki/Special:SearchCenter or /index.php?title=Special:SearchCenter). This is the page where the vulnerable search functionality resides.
    Affected if The Special:SearchCenter page is accessible and functional in the wiki
  4. Test for reflected XSS via search parameter
    Navigate to Special:SearchCenter with a test search term containing HTML/script, for example: /wiki/Special:SearchCenter?search=<script>alert('XSS')</script>. Observe whether the search term is reflected unencoded in the page response.
    Affected if The search term parameter value is rendered in the page HTML without encoding or escaping, allowing script execution

You are affected if Hallowelt Bluespice is installed with a version in the range >= 3.0 to < 3.2.9 or exactly version 4.1.0, the ExtendedSearch extension is enabled, and the Special:SearchCenter page reflects URL search parameters without proper encoding.

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 3.2.9 or later
Fixed in 3.2.9
Interim mitigation

Implement proper output encoding/escaping on the search term before rendering it on the Special:SearchCenter page, and validate/sanitize search input.

Recommended fix Moderate confidence

Bluespice 3.2.9 or later for 3.x line; Bluespice 4.1.1 or later for 4.x line

  1. 1. Identify the currently installed Bluespice version by checking the version number in the software or administration panel.
  2. 2. If running Bluespice version 3.0 through 3.2.8, plan to upgrade to version 3.2.9 or later.
  3. 3. If running Bluespice version 4.1.0, plan to upgrade to the next available stable release after 4.1.0 (e.g., 4.1.1 or later).
  4. 4. Before upgrading, backup the entire database and file system.
  5. 5. Review the Bluespice upgrade documentation for your specific version line.
  6. 6. Perform the upgrade following the standard upgrade procedure for Bluespice.
  7. 7. After upgrade, verify that the Special:SearchCenter page is accessible and the XSS vulnerability is resolved by testing with a benign search query.
Caveat Review release notes for 3.2.9 and subsequent 4.x releases for any breaking changes or migration requirements

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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