VulnerabilityPublished 29 May 2022Updated 30 May 2025

CVE-2022-24967: XSS

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium · fixed in 3.7.0 : update affected systems when convenient.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.7.0

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

Attack Complexity: Low
Attack Vector: Network
Availability: Low
Confidentiality: Low
Integrity: Low
Privileges Required: Low
Scope: Changed
User Interaction: Required

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 May 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
n/a n/a	Affected <3.7.0	Fixed in 3.7.0

AI-suggested

1. Upgrade Black Rainbow NIMBUS to version 3.7.0 or later, where the vulnerability is fixed. 2. If immediate upgrade is not possible, implement strict input validation and output encoding on all user-supplied data to prevent script injection and execution. 3. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 4. Conduct regular security audits and penetration testing focusing on XSS vectors within the application. 5. Educate users about phishing and social engineering tactics to reduce the risk of triggering malicious payloads. 6. Monitor application logs for unusual activity that could indicate exploitation attempts. 7. Use web application firewalls (WAFs) configured to detect and block XSS attack patterns as an additional layer of defense.

Description

Black Rainbow NIMBUS before 3.7.0 allows stored Cross-site Scripting (XSS).

Impact

For European organizations using Black Rainbow NIMBUS, this vulnerability could lead to unauthorized disclosure of sensitive information, session hijacking, and potential compromise of user accounts or administrative functions. Given the stored nature of the XSS, attackers can craft persistent malicious payloads that affect multiple users over time. This could result in reputational damage, regulatory non-compliance (e.g., GDPR violations due to data breaches), and operational disruptions. Organizations in sectors with high regulatory scrutiny such as finance, healthcare, and government are particularly at risk. The requirement for user interaction means phishing or social engineering could be used to lure users into triggering the exploit. The medium severity score suggests a moderate but tangible risk that should be addressed promptly to avoid escalation or chaining with other vulnerabilities.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 15:41 UTC

Technical details

References

Community reviews

Related threats