LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2511: Potential XSS in title URL parameter

Cross-site Scripting (XSS) vulnerability in the "commonuserinterface" component of BlueSpice allows an attacker to inject arbitrary HTML into a page using the title parameter of the call URL.

MediumCVSS 4.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

BlueSpice 4 has a cross-site scripting flaw where a crafted page URL can inject HTML through the title parameter. A victim must interact with the malicious link or page. Business impact is limited but real: exposed wiki users could have page content manipulated or some browser-accessible data disclosed.

Executive priority

Handle in the normal vulnerability remediation cycle, faster for public-facing BlueSpice 4 systems. This is not a critical emergency based on provided evidence, but XSS in collaboration tools can still create credible user-trust and data-exposure risk.

Technical view

CVE-2022-2511 affects the BlueSpice commonuserinterface component in version 4. The issue is CWE-79 XSS via the call URL title parameter. CVSS 3.1 is 4.3: network reachable, low complexity, no privileges, user interaction required, unchanged scope, low confidentiality impact only.

Likely exposure

Organizations running BlueSpice 4 are the stated affected population. Exposure is more relevant for internet-facing or broadly accessible wiki deployments where an unauthenticated attacker can get a user to open a crafted URL.

Exploitation context

The source bundle does not show known active exploitation, and the CVE is not marked KEV. The attacker needs user interaction. Provided evidence supports HTML injection risk, but does not provide exploit prevalence or weaponization status.

Researcher notes

Evidence is concise and specific: affected product BlueSpice 4, component commonuserinterface, vector title URL parameter, CWE-79, CVSS 4.3. The bundle does not include a named fixed version, workaround, or exploitation evidence, so remediation should be anchored to the vendor advisory.

Mitigation direction

  • Identify all BlueSpice 4 deployments and their exposure level.
  • Review the Hallo Welt! BlueSpice advisory for fixed versions or vendor workarounds.
  • Update BlueSpice according to vendor guidance when a fixed release is confirmed.
  • Restrict external access to affected wiki instances where operationally possible.
  • Use WAF or input filtering only as temporary compensating control.

Validation and detection

  • Confirm whether each wiki is running BlueSpice version 4.
  • Check whether the commonuserinterface component is present and enabled.
  • Review web logs for suspicious title parameter values containing markup.
  • Verify vendor advisory status against the deployed BlueSpice release.
  • Test remediation using safe, non-executing input only.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-2511 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2022-2511Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Hallo Welt! GmbHBlueSpice4Listed
Weakness

CWE details

CWE-79

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.