What is CVE-2025-68457?

CVE-2025-68457 is a low-severity cross-site scripting (XSS) vulnerability in orejime (npm), affecting versions < 2.3.2. It is fixed in 2.3.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2025-68457?

CVE-2025-68457 has a CVSS score of 6.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of orejime are affected by CVE-2025-68457?

orejime (npm) versions < 2.3.2 is affected.

Is there a fix for CVE-2025-68457?

Yes. CVE-2025-68457 is fixed in 2.3.2. Upgrade to this version or later.

Is CVE-2025-68457 exploitable, and should I be worried?

Whether CVE-2025-68457 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-68457 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-68457?

Upgrade orejime to 2.3.2 or later.

CVE-2025-68457 in orejime

Q: How severe is CVE-2025-68457?

CVE-2025-68457 has a CVSS score of 6.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of orejime are affected by CVE-2025-68457?

orejime (npm) versions < 2.3.2 is affected.

Q: Is there a fix for CVE-2025-68457?

Yes. CVE-2025-68457 is fixed in 2.3.2. Upgrade to this version or later.

Q: Is CVE-2025-68457 exploitable, and should I be worried?

Whether CVE-2025-68457 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-68457 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-68457?

Upgrade orejime to 2.3.2 or later.

Summary

Orejime has executable code in HTML attributes

Workarounds

The problem can be fixed outside of Orejime by sanitizing attributes which could contain executable code.

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2025-68457 has a CVSS score of 6.1 (Low). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.3.2); upgrading removes the vulnerable code path.

Affected versions

orejime (< 2.3.2)

Security releases

orejime → 2.3.2 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The problem has been patched by https://github.com/boscop-fr/orejime/pull/143. It is available in version 2.3.2.

Frequently Asked Questions

What is CVE-2025-68457? CVE-2025-68457 is a low-severity cross-site scripting (XSS) vulnerability in orejime (npm), affecting versions < 2.3.2. It is fixed in 2.3.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2025-68457? CVE-2025-68457 has a CVSS score of 6.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of orejime are affected by CVE-2025-68457? orejime (npm) versions < 2.3.2 is affected.
Is there a fix for CVE-2025-68457? Yes. CVE-2025-68457 is fixed in 2.3.2. Upgrade to this version or later.
Is CVE-2025-68457 exploitable, and should I be worried? Whether CVE-2025-68457 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-68457 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-68457? Upgrade orejime to 2.3.2 or later.