smartbanner.js rel noopener XSS vulnerability
smartbanner.js is a customizable smart app banner for iOS and Android. Prior to version 1.14.1, clicking on smartbanner `View` link and navigating to 3rd party page leaves `window.opener` exposed. It may allow hostile third parties to abuse `window.opener`, e.g. by redirection or injection on the original page with smartbanner. `rel="noopener"` is automatically populated to links as of `v1.14.1` which is a recommended upgrade to resolve the vulnerability. Some workarounds are available for those who cannot upgrade. 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 third 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. Version 1.14.1 of smartbanner.js contains a fix for the issue.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2025-25300
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 13:48 UTC · Revision 1
Source evidence
smartbanner.js rel noopener XSS vulnerability
core-osv · Original sourcePublished 18 Feb 2025, 17:38 UTC
smartbanner.js is a customizable smart app banner for iOS and Android. Prior to version 1.14.1, clicking on smartbanner `View` link and navigating to 3rd party page leaves `window.opener` exposed. It may allow hostile third parties to abuse `window.opener`, e.g. by redirection or injection on the original page with smartbanner. `rel="noopener"` is automatically populated to links as of `v1.14.1` which is a recommended upgrade to resolve the vulnerability. Some workarounds are available for those who cannot upgrade. 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 third 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. Version 1.14.1 of smartbanner.js contains a fix for the issue.
osv:CVE-2025-25300
Complete source record
{
"id": "0389fc3b2ad43ccdaac366aef968bd2dcb19520b4ae0c6779d2abe0c4ff06978",
"url": "https://osv.dev/vulnerability/CVE-2025-25300",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "smartbanner.js rel noopener XSS vulnerability",
"summary": "smartbanner.js is a customizable smart app banner for iOS and Android. Prior to version 1.14.1, clicking on smartbanner `View` link and navigating to 3rd party page leaves `window.opener` exposed. It may allow hostile third parties to abuse `window.opener`, e.g. by redirection or injection on the original page with smartbanner. `rel=\"noopener\"` is automatically populated to links as of `v1.14.1` which is a recommended upgrade to resolve the vulnerability. Some workarounds are available for those who cannot upgrade. 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 third 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. Version 1.14.1 of smartbanner.js contains a fix for the issue.",
"evidence": "osv:CVE-2025-25300",
"products": [],
"severity": "low",
"structured": {
"id": "CVE-2025-25300",
"aliases": [
"CVE-2025-25300",
"GHSA-9mrq-cjgh-32g2"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N/E:U"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/ain/smartbanner.js",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "90c6a341d541c4c00c004d97b112e4b39ad972aa"
},
{
"fixed": "fce8c31dfe04033d9d005a89694d3e7a60784f89"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "1.14.1"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "fce8c31dfe04033d9d005a89694d3e7a60784f89"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v1.14.0",
"v1.13.0",
"v1.12.0",
"v1.11.0",
"v1.10.1",
"v1.10.0",
"v1.9.1",
"v1.9.0",
"v1.8.0",
"v1.7.0",
"v1.6.0",
"v1.5.0",
"v1.4.1",
"v1.4.0",
"v1.3.0",
"v1.2.0",
"v1.1.1",
"v1.1.0",
"v1.0.3",
"v1.0.2",
"v1.0.1",
"v1.0.0",
"v0.0.1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-25300.json"
}
}
],
"modified": "2026-10-28T02:30:35.949901952Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/25xxx/CVE-2025-25300.json",
"https://github.com/ain/smartbanner.js/security/advisories/GHSA-9mrq-cjgh-32g2",
"https://nvd.nist.gov/vuln/detail/CVE-2025-25300",
"https://github.com/ain/smartbanner.js/commit/fce8c31dfe04033d9d005a89694d3e7a60784f89"
],
"provider_metadata": {
"cwe_ids": [
"CWE-601",
"CWE-79"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/25xxx/CVE-2025-25300.json"
}
},
"related_cves": [
{
"value": "CVE-2025-25300",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 503296,
"published_at": "2025-02-18T17:38:52.088+00:00"
}