CVE-2019-14470

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

Score 6.1 from GitHub Security Advisory published 2022-05-24. NVD baseline CVSS 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
6.1
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 83%
CISA-KEV: Not listedEPSS: 83%CVSS: 6.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

cosenary Instagram-PHP-API (aka Instagram PHP API V2), as used in the UserPro plugin through 4.9.32 for WordPress, has XSS via the example/success.php error_description parameter.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
99.6%
KEV
Not listed

Published

September 4, 2019

Last Modified

November 21, 2024

References (8)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
composercosenary/instagram—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
cosenary/instagramv2.2, v2.3——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:24 UTCEPSS rescore
  2. 2026-07-09 19:06 UTCEPSS rescore
  3. 2026-07-04 06:28 UTCEPSS rescore
  4. 2026-07-04 06:28 UTCEPSS rescore
  5. 2026-07-01 15:03 UTCEPSS rescore
  6. 2026-07-01 15:03 UTCEPSS rescore
  7. 2026-06-28 04:54 UTCEPSS rescore
  8. 2026-06-28 04:53 UTCEPSS rescore
  9. 2026-06-25 13:47 UTCEPSS rescore
  10. 2026-06-25 13:47 UTCEPSS rescore
  11. 2026-06-23 21:30 UTCEPSS rescore
  12. 2026-06-23 21:30 UTCEPSS rescore
  13. 2026-06-22 14:23 UTCEPSS rescore
  14. 2026-06-22 14:23 UTCEPSS rescore
  15. 2026-06-21 14:54 UTCEPSS rescore
  16. 2026-06-21 14:54 UTCEPSS rescore
  17. 2026-06-21 01:57 UTCEPSS rescore
  18. 2026-06-21 01:57 UTCEPSS rescore
  19. 2026-06-17 17:50 UTCEPSS rescore
  20. 2026-06-15 17:45 UTCEPSS rescore
  21. 2026-06-14 23:15 UTCEPSS rescore
  22. 2026-06-14 23:15 UTCEPSS rescore
  23. 2026-06-13 22:58 UTCEPSS rescore
  24. 2026-06-12 23:09 UTCEPSS rescore
  25. 2026-06-11 13:58 UTCEPSS rescore
Show 29 more
  1. 2026-06-11 13:58 UTCEPSS rescore
  2. 2026-06-10 22:16 UTCEPSS rescore
  3. 2026-06-10 13:19 UTCEPSS rescore
  4. 2026-06-08 14:15 UTCEPSS rescore
  5. 2026-06-08 14:14 UTCEPSS rescore
  6. 2026-06-07 15:23 UTCEPSS rescore
  7. 2026-06-07 15:22 UTCEPSS rescore
  8. 2026-06-06 13:45 UTCEPSS rescore
  9. 2026-06-06 13:45 UTCEPSS rescore
  10. 2026-06-05 22:45 UTCEPSS rescore
  11. 2026-06-05 22:45 UTCEPSS rescore
  12. 2026-06-05 06:08 UTCEPSS rescore
  13. 2026-06-05 06:08 UTCEPSS rescore
  14. 2026-06-04 13:10 UTCEPSS rescore
  15. 2026-06-04 13:10 UTCEPSS rescore
  16. 2026-06-02 20:11 UTCEPSS rescore
  17. 2026-06-01 13:50 UTCEPSS rescore
  18. 2026-06-01 13:50 UTCEPSS rescore
  19. 2026-05-31 22:29 UTCEPSS rescore
  20. 2026-05-31 22:29 UTCEPSS rescore
  21. 2026-05-31 00:14 UTCEPSS rescore
  22. 2026-05-31 00:14 UTCEPSS rescore
  23. 2026-05-29 13:42 UTCEPSS rescore
  24. 2026-05-28 13:43 UTCEPSS rescore
  25. 2026-05-27 14:57 UTCEG score recompute
  26. 2026-05-27 14:57 UTCGHSA enrichment
  27. 2026-05-27 13:38 UTCEPSS rescore
  28. 2026-05-26 13:42 UTCEPSS rescore
  29. 2026-05-26 13:42 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-47304
    First seen Aug 26, 2019

    WordPress Plugin UserPro 4.9.32 - Cross-Site Scripting

    Open source ↗
  • Nucleihttp/cves/2019/CVE-2019-14470.yaml
    First seen Jan 1, 2019

    WordPress UserPro 4.9.32 - Cross-Site Scripting

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-14470?
CVE-2019-14470 is a medium vulnerability published on September 4, 2019. cosenary Instagram-PHP-API (aka Instagram PHP API V2), as used in the UserPro plugin through 4.9.32 for WordPress, has XSS via the example/success.php error_description parameter.
When was CVE-2019-14470 disclosed?
CVE-2019-14470 was first published in the National Vulnerability Database on September 4, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-14470 actively exploited?
CVE-2019-14470 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-14470?
CVE-2019-14470 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2019-14470?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-14470, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-14470

Explore →

Is Your Infrastructure Affected by CVE-2019-14470?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs