dbcve.org
Cordova InappbrowserApplication · Apache

CVE-2026-47430

HIGH · 7.5 CVSS v3.1 Published 2026-06-08
Fix available
A fix is available. Upgrade to 6.0.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
## 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.cordova_iab.postMessage({id: '<victim-callback-id>', d: '...'})` to fire callbacks belonging to any other installed Cordova plugin (Camera, Contacts, File, Geolocation). Cordova callback IDs follow the predictable format `<PluginName><sequential-integer>`, making enumeration feasible. Successful exploitation allows the attacker to spoof plugin results across trust boundaries — for example, injecting a forged camera approval, a fabricated contacts list, or a crafted file-read response. This issue affects Cordova Plugin InAppBrowser: from 3.1.0 through 6.0.0. Users are recommended to upgrade to version 6.0.1, which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The iOS implementation of cordova-plugin-inappbrowser passes the id field from WKScriptMessage bodies to Cordova's callback system without validating the format, allowing any web content loaded in the InAppBrowser to invoke arbitrary pending plugin callbacks by guessing or enumerating the predictable callback ID format (<PluginName><sequential-integer>). This enables spoofing plugin responses for Camera, Contacts, File, Geolocation, and other Cordova plugins.

MitigationUpgrade cordova-plugin-inappbrowser to version 6.0.1 or later, which implements proper format validation on the callback ID before passing it to the Cordova command delegate.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cordova InappbrowserApplication
Affected:>= 3.1.0, < 6.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate cordova-plugin-inappbrowser version
    Check the installed version by inspecting the plugin's package.json in the plugins folder (e.g., plugins/cordova-plugin-inappbrowser/package.json) or by running 'cordova plugin list' in the project directory
    Affected if The plugin version is 3.1.0 or higher but lower than 6.0.1
  2. Confirm iOS platform is targeted
    Verify the project targets iOS by checking for the ios platform in config.xml or by running 'cordova platform list'
    Affected if The iOS platform is added to the project (the vulnerability exists only in the iOS WKWebView implementation)
  3. Verify WKWebView is in use
    Check if WKWebView is enabled for Cordova (look for CordovaWKWebViewEngine in config.xml or UIWebViewDelegate references being absent)
    Affected if WKWebView engine is configured for Cordova iOS (the flaw is in CDVWKInAppBrowser.m, the WKWebView-specific handler)
  4. Check if InAppBrowser is actively used
    Search project source code for references to InAppBrowser (window.open with InAppBrowser, cordova.InAppBrowser.open, or the plugin being whitelisted in config.xml)
    Affected if The InAppBrowser plugin is installed and the app uses it to load external web content

A user is affected if cordova-plugin-inappbrowser version is between 3.1.0 and 6.0.0 inclusive, the iOS platform is targeted, WKWebView is used, and the app loads external content via InAppBrowser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.0.1 or later
Fixed in 6.0.1
Interim mitigation

Upgrade cordova-plugin-inappbrowser to version 6.0.1 or later, which implements proper format validation on the callback ID before passing it to the Cordova command delegate.

Recommended fix High confidence

6.0.1

  1. Identify the Cordova project that uses cordova-plugin-inappbrowser
  2. Open a terminal in the project root directory
  3. Remove the vulnerable plugin: cordova plugin remove cordova-plugin-inappbrowser
  4. Install the fixed version: cordova plugin add [email protected]
  5. Rebuild the iOS platform: cordova platform remove ios && cordova platform add ios
  6. Build the iOS app: cordova build ios
  7. Test the InAppBrowser functionality to verify the upgrade does not break existing features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cordova Inappbrowser Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47430 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47430 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data