Skip to content

← Public intelligence

npm package

smartbanner.js

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 2.7npmAmendedPublished

    smartbanner.js rel noopener vulnerability

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

    Affected
    • npm smartbanner.js < 1.14.1
    Fixed in
    1.14.1· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 1.14.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →