CVE REMEDIATION GUIDE
Review reviewCriticalFixed-version data available

CVE-2026-47430 remediation guide

Apache Software Foundation Cordova Plugin InAppBrowser, cordova 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 configuratio...

Open CVE record
ProductApache Software Foundation Cordova Plugin InAppBrowser, cordova inappbrowser
Affected versions>= 3.1.0 <= 6.0.0, >= 3.1.0 < 6.0.1
Fixed versions6.0.1
Priority basisReview · CVSS 9.5 · EPSS 0.72%
01

Identify the affected asset

Confirm whether Apache Software Foundation Cordova Plugin InAppBrowser, cordova inappbrowser is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 3.1.0 <= 6.0.0, >= 3.1.0 < 6.0.1. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 6.0.1. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.