CVE-2026-47430: CWE-20 Improper Input Validation in Apache Software Foundation Cordova Plugin InAppBrowser
## 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.
AI Analysis
Technical Summary
The vulnerability arises from the iOS Cordova Plugin InAppBrowser passing the 'id' field from WKScriptMessage bodies directly to the commandDelegate's sendPluginResult:callbackId: method without validating the format. This allows any web content loaded inside the InAppBrowser to invoke pending Cordova callbacks by posting messages with guessable or enumerated callback IDs. Since Cordova callback IDs follow a predictable pattern, an attacker can craft messages to trigger callbacks of other installed plugins (e.g., Camera, Contacts, File, Geolocation). Exploitation enables spoofing of plugin results across trust boundaries, potentially injecting forged approvals or fabricated data responses. The issue affects versions 3.1.0 through 6.0.0 of the plugin and is fixed in version 6.0.1.
Potential Impact
An unauthenticated remote attacker who controls web content displayed in the InAppBrowser can invoke arbitrary Cordova plugin callbacks by guessing callback IDs. This can lead to spoofing of plugin results such as fake camera approvals, fabricated contacts lists, or crafted file-read responses. The vulnerability breaks trust boundaries within the host app, potentially misleading the app about user permissions or data integrity. The CVSS 4.0 score of 9.5 reflects the critical nature of this impact.
Mitigation Recommendations
Users should upgrade to Apache Cordova Plugin InAppBrowser version 6.0.1 or later, which fixes this vulnerability. No other mitigations are indicated. Patch status is confirmed by the vendor's recommendation to upgrade to 6.0.1. Until upgraded, avoid loading untrusted web content in the InAppBrowser to reduce exposure.
CVE-2026-47430: CWE-20 Improper Input Validation in Apache Software Foundation Cordova Plugin InAppBrowser
Description
## 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.
CVSS v4.0
Score 9.5critical
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises from the iOS Cordova Plugin InAppBrowser passing the 'id' field from WKScriptMessage bodies directly to the commandDelegate's sendPluginResult:callbackId: method without validating the format. This allows any web content loaded inside the InAppBrowser to invoke pending Cordova callbacks by posting messages with guessable or enumerated callback IDs. Since Cordova callback IDs follow a predictable pattern, an attacker can craft messages to trigger callbacks of other installed plugins (e.g., Camera, Contacts, File, Geolocation). Exploitation enables spoofing of plugin results across trust boundaries, potentially injecting forged approvals or fabricated data responses. The issue affects versions 3.1.0 through 6.0.0 of the plugin and is fixed in version 6.0.1.
Potential Impact
An unauthenticated remote attacker who controls web content displayed in the InAppBrowser can invoke arbitrary Cordova plugin callbacks by guessing callback IDs. This can lead to spoofing of plugin results such as fake camera approvals, fabricated contacts lists, or crafted file-read responses. The vulnerability breaks trust boundaries within the host app, potentially misleading the app about user permissions or data integrity. The CVSS 4.0 score of 9.5 reflects the critical nature of this impact.
Mitigation Recommendations
Users should upgrade to Apache Cordova Plugin InAppBrowser version 6.0.1 or later, which fixes this vulnerability. No other mitigations are indicated. Patch status is confirmed by the vendor's recommendation to upgrade to 6.0.1. Until upgraded, avoid loading untrusted web content in the InAppBrowser to reduce exposure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-05-19T19:48:39.914Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a26a89be29bf47b50de241f
Added to database: 6/8/2026, 11:33:47 AM
Last enriched: 6/8/2026, 11:48:32 AM
Last updated: 6/8/2026, 1:40:14 PM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.