{“lastseen”:””,”description”:”## Summary\\n\\nThe 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\u2013574`). 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.\\n\\n\\n## Impact\\n\\nAn unauthenticated remote attacker who controls content displayed in the InAppBrowser \u2014 via a URL the app opens (OAuth redirect, marketing link, deep-link target) or a network interception \u2014 can call `window.webkit.messageHandlers.cordova_iab.postMessage({id: ‘\\u003cvictim-callback-id\\u003e’, d: ‘…’})` to fire callbacks belonging to any other installed Cordova plugin (Camera, Contacts, File, Geolocation). Cordova callback IDs follow the predictable format `\\u003cPluginName\\u003e\\u003csequential-integer\\u003e`, making enumeration feasible. Successful exploitation allows the attacker to spoof plugin results across trust boundaries \u2014 for example, injecting a forged camera approval, a fabricated contacts list, or a crafted file-read response.\\n\\nThis issue affects Cordova Plugin InAppBrowser: from 3.1.0 through 6.0.0.\\n\\nUsers are recommended to upgrade to version 6.0.1, which fixes the issue.”,”published”:”2026-06-08T10:22:25.138Z”,”modified”:”2026-06-08T10:22:25.138Z”,”type”:”cve”,”title”:”Cordova Plugin InAppBrowser: iOS: Arbitrary Cordova callback IDs can be dispatched without validation from InAppBrowser WebViews”,”source”:”apache”,”references”:”https:\/\/lists.apache.org\/thread\/sb539nss3b0545wnyt1pbh7zgwjvz2qq”,”id”:”CVE-2026-47430″,”bulletinFamily”:””,”cwe”:[“CWE-20″],”cvelist”:null,”sourceData”:”Apache Software Foundation Cordova Plugin InAppBrowser 3.1.0″,”sourceHref”:””,”cvss”:{“score”:9.5,”severity”:”CRITICAL”,”vector”:”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”,”version”:”4.0″},”cvss2″:{},”cvss3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””,”cvssV3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””}},”href”:””,”category_name”:”CVE”,”post_link”:””,”product”:”Cordova Plugin InAppBrowser”,”version”:”3.1.0″,”vendor”:”Apache Software Foundation”,”ai_description”:”Arbitrary Cordova callback IDs can be dispatched without validation from InAppBrowser WebViews, allowing an attacker to spoof plugin results across trust boundaries.”,”ai_severity”:”Critical”,”ai_vendor”:”Apache Software Foundation”,”ai_product”:”Cordova Plugin InAppBrowser”,”ai_version”:”3.1.0-6.0.0″,”ai_score”:9.5}<\/p>\n","protected":false},"excerpt":{"rendered":"
{“lastseen”:””,”description”:”## Summary\\n\\nThe 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\u2013574`). Any web content…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[9,6,8,149,12,13,7,11,5],"class_list":["post-60664","post","type-post","status-publish","format-standard","hentry","category-category_cve","tag-critical","tag-cve","tag-cvss","tag-cvss-95","tag-exploit","tag-news","tag-security","tag-tapic","tag-vulnerability"],"yoast_head":"\n