What is CVE-2025-25300?

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

Which versions of smartbanner.js are affected by CVE-2025-25300?

smartbanner.js (npm) versions < 1.14.1 is affected.

Is there a fix for CVE-2025-25300?

Yes. CVE-2025-25300 is fixed in 1.14.1. Upgrade to this version or later.

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

Whether CVE-2025-25300 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-25300 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-25300?

Upgrade smartbanner.js to 1.14.1 or later.

CVE-2025-25300 in smartbanner.js

Q: Which versions of smartbanner.js are affected by CVE-2025-25300?

smartbanner.js (npm) versions < 1.14.1 is affected.

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

Yes. CVE-2025-25300 is fixed in 1.14.1. Upgrade to this version or later.

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

Whether CVE-2025-25300 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-25300 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-25300?

Upgrade smartbanner.js to 1.14.1 or later.

Summary

smartbanner.js rel noopener vulnerability

rel noopener vulnerability

Workarounds

If you can not upgrade to v1.14.1:

Ensure View link is only taking users to App Store or Google Play Store where security is guarded by respective app store security teams
If View link is going to a 3rd party page, limit smartbanner.js to be used on iOS that decreases the scope of the vulnerability since as of Safari 12.1, rel="noopener" is imposed on all target="_blank" links.

Following combination of smartbanner meta tags can be used to achieve the above:
```
<meta name="smartbanner:enabled-platforms" content="none">
<meta name="smartbanner:include-user-agent-regex" content="Mobile.*Safari">
```

References

For more information

If you have any questions or comments about this advisory:

Open an issue in smartbanner.js

Impact

Clicking on smartbanner View link and navigating to 3rd party page leaves window.opener exposed. It may allow hostile 3rd parties to abuse window.opener, e.g. by redirection or injection on the original page with smartbanner.

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.

Affected versions

smartbanner.js (< 1.14.1)

Security releases

smartbanner.js → 1.14.1 (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

rel="noopener" is automatically populated to links as of v1.14.1 which is a recommended upgrade to resolve the vulnerability.

Frequently Asked Questions

What is CVE-2025-25300? CVE-2025-25300 is a low-severity cross-site scripting (XSS) vulnerability in smartbanner.js (npm), affecting versions < 1.14.1. It is fixed in 1.14.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
Which versions of smartbanner.js are affected by CVE-2025-25300? smartbanner.js (npm) versions < 1.14.1 is affected.
Is there a fix for CVE-2025-25300? Yes. CVE-2025-25300 is fixed in 1.14.1. Upgrade to this version or later.
Is CVE-2025-25300 exploitable, and should I be worried? Whether CVE-2025-25300 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-25300 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-25300? Upgrade smartbanner.js to 1.14.1 or later.