How severe is CVE-2012-5881?

No CVSS score has been assigned to CVE-2012-5881 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-5881?

CVE-2012-5881 affects the following packages: yui2 (npm). Ecosystems affected: npm.

How do I fix CVE-2012-5881?

The records we use list no patched version of yui2 for CVE-2012-5881. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2012-5881 in my npm dependencies?

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

How do I mitigate CVE-2012-5881 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-2012-5881 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-5881 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-2012-5881?

CVE-2012-5881 has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 84th 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-2012-5881?

CVE-2012-5881 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-2012-5881 published, and has it been updated?

CVE-2012-5881 was published on May 17, 2022 and was last updated on January 9, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2012-5881 — yui2

CVE-2012-5881 is a Cross-site Scripting (XSS) vulnerability in yui2. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Cross-site scripting in yui 2.4.0

Published

May 17, 2022

Updated

Jan 9, 2024

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

yui2npm

287downloads / week

Description

Cross-site scripting (XSS) vulnerability in the Flash component infrastructure in YUI 2.4.0 through 2.9.0 allows remote attackers to inject arbitrary web script or HTML via vectors related to charts.swf, a similar issue to CVE-2010-4207.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`yui2`	≥ 2.4.0	No fix

Affected Products

1 product · 14 configurations

Application

yuiyahoo

11 versions

2.4.02.4.12.5.02.5.12.5.22.6.02.7.02.8.02.8.12.8.22.9.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yui2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of yui2 for CVE-2012-5881. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-5881 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works