How severe is CVE-2022-23515?

CVE-2022-23515 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-23515?

CVE-2022-23515 affects the following packages: loofah (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2022-23515?

Update loofah to 2.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23515 is resolved across your whole dependency graph.

How do I detect CVE-2022-23515 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loofah, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-23515 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2022-23515 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-23515 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-23515?

CVE-2022-23515 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-23515?

CVE-2022-23515 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-23515 published, and has it been updated?

CVE-2022-23515 was published on December 14, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎

💎 RubyGems

Not in CISA KEV

MEDIUM severity

CVE-2022-23515 — loofah

MEDIUMFix: flavorjones/loofah@415677f

CVE-2022-23515 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in loofah. A fix is available for loofah — see the affected versions and patch details below.

Improper neutralization of data URIs may allow XSS in Loofah

Also known asGHSA-228g-948r-83gx

Published

Dec 14, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

💎loofah

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Loofah >= 2.1.0, < 2.19.1 is vulnerable to cross-site scripting via the image/svg+xml media type in data URIs.

Mitigation

Upgrade to Loofah >= 2.19.1.

Severity

The Loofah maintainers have evaluated this as Medium Severity 6.1.

References

Credit

This vulnerability was responsibly reported by Maciej Piechota (@haqpl).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`loofah`	≥ 2.1.0&&< 2.19.1	2.19.1`bundle update loofah --conservative`

Affected Products

2 products · 2 configurations

debian linuxdebian

1 version

10.0

Application

loofahloofah_project

≥ 2.1.0 && < 2.19.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loofah, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update loofah to 2.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23515 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Satellite 6.13 for RHEL 8	`satellite:el8/rubygem-loofah-0:2.19.1-1.el8sat`	RHSA-2023:2097

Frequently Asked Questions

## Summary Loofah `>= 2.1.0, < 2.19.1` is vulnerable to cross-site scripting via the `image/svg+xml` media type in data URIs. ## Mitigation Upgrade to Loofah `>= 2.19.1`. ## Severity The Loofah maintainers have evaluated this as [Medium Severity 6.1](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N). ## References - [CWE - CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (4.9)](https://cwe.mitre.org/data/definitions/79.html) - [SVG MIME Type (image/svg+xml) is misleading to developers · Issue #266 · w3c

O3 Security · Impact-Aware SCA

Is CVE-2022-23515 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

loofah

6.9/10

Maintained10/10

Code-Review0/10

Branch-ProtectionN/A

Assessed Oct 26, 2026

Timeline

Disclosed

Dec 14, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-23515

GHSA-228g-948r-83gx

References

Advisorygithub.com · CVE 2022 23515.json Advisorygithub.com · GHSA 228g 948r 83gx Advisorynvd.nist.gov · CVE 2022 23515 Reportgithub.com Webhackerone.com Weblists.debian.org · msg00011 Weblists.debian.org · msg00044 Webgithub.com Webgithub.com · 415677f3cf7f9254f42f811e784985cd63c7407f Webgithub.com · CVE 2022 23515.yml Packagegithub.com · loofah

Related vulnerabilities

This CVE is medium severity; 4 of 8 other CVEs affecting loofah are rated as high or higher (top: high).

GHSA-5qhf-9phg-95m2CVE-2026-73491CVE-2026-73490GHSA-2j22-pr5w-6gq8GHSA-46fp-8f5p-pf2mCVE-2022-23516CVE-2022-23514CVE-2019-15587

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-23515 — loofah

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Summary

Mitigation

Severity

References

Credit

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-23515 in your dependencies?