CVE-2025-68457 — orejime
Fix: boscop-fr/orejime#143CVE-2025-68457 is a Cross-site Scripting (XSS) vulnerability in orejime. A fix is available for orejime — see the affected versions and patch details below.
Orejime has executable code in HTML attributes
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-68457.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
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.
orejimenpmDescription
Impact
On HTML elements handled by Orejime, one could run malicious code by embedding javascript: code within data attributes.
When consenting to the related purpose, Orejime would turn data attributes into unprefixed ones (i.e. data-href into href), thus executing the code.
This shouldn't have any impact on most setups, as elements handled by Orejime are generally hardcoded. The problem would only arise if somebody could inject HTML code within pages.
See https://github.com/boscop-fr/orejime/issues/142 for the original report.
Patches
The problem has been patched by https://github.com/boscop-fr/orejime/pull/143. It is available in version 2.3.2.
Workarounds
The problem can be fixed outside of Orejime by sanitizing attributes which could contain executable code.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | orejime | all versions | 2.3.2npm install orejime@2.3.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for orejime, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update orejime to 2.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-68457 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-68457 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-68457. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-68457 in your dependencies?
O3 Security finds CVE-2025-68457 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.