Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.7amended

smartbanner.js rel noopener vulnerability

CVE-2025-25300GHSA-9mrq-cjgh-32g2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (smartbanner.js 1.14.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N/E:U · score source
EPSS
  • CVE-2025-25300: 0.42% estimated exploitation activity in the next 30 days; percentile 36.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

rel noopener vulnerability 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. Patches rel="noopener" is automatically populated to links as of v1.14.1 which is a recommended upgrade to resolve the vulnerability. Workarounds If you can not upgrade to v1.14.1: 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 2. 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: References About rel=noopener Safari 12.1 Release Notes For more information If you have any questions or comments about this…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-9mrq-cjgh-32g2

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-9mrq-cjgh-32g2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-25300

Advisory: smartbanner.js rel noopener vulnerability
IDs: CVE-2025-25300, GHSA-9mrq-cjgh-32g2
Record: https://patchnext.com/advisories/cve-2025-25300 (revision 3, source checked 26 Oct 2026, 12:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: smartbanner.js 1.14.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm smartbanner.js: affected < 1.14.1; fixed in 1.14.1

## Suggested inspection (read-only)
- `npm ls smartbanner.js --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on smartbanner.js.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9mrq-cjgh-32g2 (OSV record GHSA-9mrq-cjgh-32g2 lists affected ranges: npm smartbanner.js >=0 <1.14.1 (fixed))
- Verified: https://github.com/advisories/GHSA-9mrq-cjgh-32g2 (GitHub-reviewed advisory GHSA-9mrq-cjgh-32g2 lists affected ranges: npm smartbanner.js >=0 <1.14.1)

Commands are suggestions: review each one before running it.

Loading voting…