HIGH CVSS 7.5
Published: 2026-06-08

CVE-2026-47430

apache cordova_inappbrowser Security Advisory (CVE-2026-47430)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2026-47430?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2026-47430 impacting apache cordova_inappbrowser. Evaluated with CVSS Base Score of 7.5 (HIGH).

Original NVD Description

Source: NIST NVD
## 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 v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
None (PR:N)
Unauthenticated execution
User Interaction
None (UI:N)
Zero human interaction required
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
None (C:N)
No data confidentiality impact
Integrity
High (I:H)
Total modification of target system
Availability
None (A:N)
No system availability impact

🎯 Affected Versions Matrix

Affected Product apache / cordova_inappbrowser
Affected Versions *
Weakness Enumeration CWE-20

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2026-47430 impacting apache cordova_inappbrowser.

⚡ Nuclei Detection Template (YAML) cve-2026-47430.yaml
id: cve-2026-47430

info:
  name: apache cordova_inappbrowser - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: high
  description: |
    Automated signature & scanner for CVE-2026-47430 affecting apache cordova_inappbrowser.
    Evaluation: ## Summary

The iOS implementation of `cordova-plugin-inappbrowser` passes the `id` field from a `WKScriptMessage` body to `commandDelegate sendPlugin...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2026-47430
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
    cvss-score: 7.5
    cve-id: CVE-2026-47430
    cwe-id: CWE-20
  tags: cve,cve-2026-47430,apache,cordova_inappbrowser,high

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "cordova_inappbrowser"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2026-47430.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2026-47430
# Target: apache cordova_inappbrowser | CVSS: 7.5 (HIGH)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2026-47430 (apache cordova_inappbrowser)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against apache cordova_inappbrowser scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2026-47430.sh
# Recommended Remediation & Patching Commands for CVE-2026-47430
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install cordova_inappbrowser 2>/dev/null || \
sudo dnf upgrade cordova_inappbrowser 2>/dev/null || \
sudo yum update cordova_inappbrowser

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i cordova_inappbrowser 2>/dev/null || rpm -qa | grep -i cordova_inappbrowser

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

Authorities
  • No records filed in this category.
Distributions
  • No records filed in this category.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2026-47430 in apache cordova_inappbrowser?

Review vendor-specific security notices and update apache cordova_inappbrowser packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2026-47430?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2026-47430?

CVE-2026-47430 is classified with a CVSS 3.1 Base Score of 7.5 (HIGH). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
7.5
HIGH SEVERITY
CVE ID CVE-2026-47430
Weakness CWE-20
Vendor apache
Product cordova_inappbrowser
Published 2026-06-08
Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N