Cordova Plugin InAppBrowser: iOS: Arbitrary Cordova callback IDs can be dispatched without validation from InAppBrowser WebViews.
CVE-2026-47430GHSA-q42j-x8rq-pjg6
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (cordova-plugin-inappbrowser 6.0.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.
Affected packages
npm cordova-plugin-inappbrowser
- Affected
- < 6.0.1
- Fixed in
- 6.0.1
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-q42j-x8rq-pjg6 lists affected ranges: npm cordova-plugin-inappbrowser >=0 <6.0.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-q42j-x8rq-pjg6 lists affected ranges: npm cordova-plugin-inappbrowser >=0 <6.0.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 9.5 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H · score source
- EPSS
- CVE-2026-47430: 0.72% estimated exploitation activity in the next 30 days; percentile 54.08 (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.
Summary The iOS implementation of cordova-plugin-inappbrowser passes the id field from a WKScriptMessage body to commandDelegate sendPluginResult:callbackId: with no format validation (CDVWKInAppBrowser.m:560–574). Any web content loaded inside the InAppBrowser can fire any pending Cordova callback in the host app by posting a message whose id field is a guessable or enumerated callback identifier. An attack abusing this weakness must be tailored to the specific plugins and callback IDs the host app uses. Though an attacker with knowledge of common Cordova plugin configurations could craft reusable payloads targeting widely-adopted plugins. Impact An unauthenticated remote attacker who controls content displayed in the InAppBrowser — via a URL the app opens (OAuth redirect, marketing link, deep-link target) or a network interception — can call window.webkit.messageHandlers.cordovaiab.postMessage({id: '<victim-callback-id', d: '...'}) to fire callbacks belonging to any other installed…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 4 · amended ·
Amended from ghsa record GHSA-q42j-x8rq-pjg6
- Revision 3 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 2 · amended ·
Amended from osv record GHSA-q42j-x8rq-pjg6
- Revision 1 · created ·
Published from ghsa record GHSA-q42j-x8rq-pjg6
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-2026-47430 Advisory: Cordova Plugin InAppBrowser: iOS: Arbitrary Cordova callback IDs can be dispatched without validation from InAppBrowser WebViews. IDs: CVE-2026-47430, GHSA-q42j-x8rq-pjg6 Record: https://patchnext.com/advisories/cve-2026-47430 (revision 4, source checked 26 Oct 2026, 12:55 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: cordova-plugin-inappbrowser 6.0.1. A vendor fix does not mean a deployment is fixed. ## Affected components - npm cordova-plugin-inappbrowser: affected < 6.0.1; fixed in 6.0.1 ## Suggested inspection (read-only) - `npm ls cordova-plugin-inappbrowser --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 cordova-plugin-inappbrowser. - 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://github.com/advisories/GHSA-q42j-x8rq-pjg6 (GitHub-reviewed advisory GHSA-q42j-x8rq-pjg6 lists affected ranges: npm cordova-plugin-inappbrowser >=0 <6.0.1) - Verified: https://osv.dev/vulnerability/GHSA-q42j-x8rq-pjg6 (OSV record GHSA-q42j-x8rq-pjg6 lists affected ranges: npm cordova-plugin-inappbrowser >=0 <6.0.1 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…