Skip to content
Fencer Intel
high 8.6

CVE-2018-16202 json

Path Traversal in cordova-plugin-ionic-webview

published 7y ago modified 4mo ago also GHSA-xwjh-cp99-cj8q , EUVD-2019-0366

cvss
8.6
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.3%
EPSS 3.3% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

Directory traversal vulnerability in cordova-plugin-ionic-webview versions prior to 2.2.0 (not including 2.0.0-beta.0, 2.0.0-beta.1, 2.0.0-beta.2, and 2.1.0-0) allows remote attackers to access arbitrary files via unspecified vectors.

Patch / fix

  • npm cordova-plugin-ionic-webview 2.2.0
  • ionicframework ionic_web_view 2.2.0

Is CVE-2018-16202 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-025-01 updated cvss 6.8

GE Gas Power ToolBoxST

  • General Electric (GE) ToolBoxST OS < 07.09.07C
    affected: mitigation “GE upgraded the Ionic library in ToolBoxST Version 7.8.0 to resolve CVE-2018-16202” ge.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

3.31% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm cordova-plugin-ionic-webview
<2.2.0
2.2.0

Affected products

  • npm, Inc. cordova-plugin-ionic-webview

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.