GHSA-c6pw-q7f2-97hv — cordova-plugin-inappbrows…
CRITICALGHSA-c6pw-q7f2-97hv is a critical-severity (CVSS 9.8) vulnerability in cordova-plugin-inappbrowser. A fix is available for cordova-plugin-inappbrowser — see the affected versions and patch details below.
Privilege Escalation in cordova-plugin-inappbrowser
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-c6pw-q7f2-97hv by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
cordova-plugin-inappbrowsernpmDescription
Versions of cordova-plugin-inappbrowser prior to 3.1.0 are vulnerable to Privilege Escalation. A website running in the InAppBrowser webview on Android could execute arbitrary JavaScript in the main application's webview using a specially crafted gap-iab: URI. This affects Cordova Android applications using the package.
Recommendation
Upgrade to version 3.1.0 or later.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | cordova-plugin-inappbrowser | all versions | 3.1.0npm install cordova-plugin-inappbrowser@3.1.0 |
Affected Products
cordova inappbrowserapacheinstantis enterprisetrackoracleretail xstore point of serviceoracleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cordova-plugin-inappbrowser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cordova-plugin-inappbrowser to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c6pw-q7f2-97hv is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is GHSA-c6pw-q7f2-97hv in your dependencies?
Find it across npm, including transitive dependencies.