CVE-2019-9787

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 39%CVSS: 8.8Exploit: Elevated riskExposed: 0

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

WordPress before 5.1.1 does not properly filter comment content, leading to Remote Code Execution by unauthenticated users in a default configuration. This occurs because CSRF protection is mishandled, and because Search Engine Optimization of A elements is performed incorrectly, leading to XSS. The XSS results in administrative access, which allows arbitrary changes to .php files. This is related to wp-admin/includes/ajax-actions.php and wp-includes/comment.php.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
62(Track)
EG Risk 62/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation44% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
39%
EPSS %ILE
99%
KEV
Not listed

Published

March 14, 2019

Last Modified

November 21, 2024

Advisory Details (7)

Auto-updated Aug 23, 2026
Patch available. Sources: github_commit.
generic

Sonar blog | Sonar

https://blog.ripstech.com/2019/wordpress-csrf-to-rce/
generic

CVE-2019-9787 - PSIRT.COM

http://www.securityfocus.com/bid/107411
generic

[SECURITY] [DSA 4677-1] wordpress security update

https://www.debian.org/security/2020/dsa-4677
generic

Version 5.1.1 – Documentation – WordPress.org

https://wordpress.org/support/wordpress-version/version-5-1-1/
generic Patch Available

WordPress 5.1.1 Security and Maintenance Release – WordPress News

https://wordpress.org/news/2019/03/wordpress-5-1-1-security-and-maintenance-release/
generic Patch Available

[SECURITY] [DLA 1742-1] wordpress security update

https://lists.debian.org/debian-lts-announce/2019/03/msg00044.html
github_commit

commit 0292de60ec78 (WordPress/WordPress)

Fix landed in WordPress/WordPress commit 0292de60ec78 — awaiting tagged release

https://github.com/WordPress/WordPress/commit/0292de60ec78c5a44956765189403654fe4d080b

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
wordpress—5.1.1+dfsg1-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
wordpress—5.1.1+dfsg1-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
wordpress—5.1.1+dfsg1-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
wordpress—5.1.1+dfsg1-1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
wordpress4.1+dfsg-1 ... 4.1.25+dfsg-1+deb8u1 (21 versions)4.1.26+dfsg-1+deb8u1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× 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.

Showing the most recent 100 of 124 total refreshes for this CVE.

  1. 2026-09-24 13:59 UTCEPSS rescore
  2. 2026-09-22 14:43 UTCEPSS rescore
  3. 2026-09-21 20:28 UTCEPSS rescore
  4. 2026-09-19 15:37 UTCEPSS rescore
  5. 2026-09-18 19:23 UTCEPSS rescore
  6. 2026-09-17 19:22 UTCEPSS rescore
  7. 2026-09-16 14:04 UTCEPSS rescore
  8. 2026-09-16 14:04 UTCEPSS rescore
  9. 2026-09-15 03:06 UTCEPSS rescore
  10. 2026-09-12 14:56 UTCEPSS rescore
  11. 2026-09-11 14:48 UTCEPSS rescore
  12. 2026-09-11 09:32 UTCEPSS rescore
  13. 2026-09-08 16:04 UTCOSV refresh
  14. 2026-09-07 15:57 UTCEPSS rescore
  15. 2026-09-06 13:44 UTCEPSS rescore
  16. 2026-09-05 15:24 UTCEPSS rescore
  17. 2026-09-04 13:56 UTCEPSS rescore
  18. 2026-09-04 05:03 UTCEPSS rescore
  19. 2026-09-02 14:08 UTCEPSS rescore
  20. 2026-09-01 03:32 UTCEPSS rescore
  21. 2026-08-30 19:14 UTCEPSS rescore
  22. 2026-08-30 01:18 UTCEPSS rescore
  23. 2026-08-28 21:37 UTCEPSS rescore
  24. 2026-08-27 14:21 UTCEPSS rescore
  25. 2026-08-26 14:42 UTCEPSS rescore
Show 75 more
  1. 2026-08-25 13:45 UTCEPSS rescore
  2. 2026-08-22 02:11 UTCOSV refresh
  3. 2026-08-20 22:51 UTCEPSS rescore
  4. 2026-08-19 17:00 UTCEPSS rescore
  5. 2026-08-18 13:44 UTCEPSS rescore
  6. 2026-08-17 13:43 UTCEPSS rescore
  7. 2026-08-16 14:52 UTCEPSS rescore
  8. 2026-08-16 02:11 UTCEPSS rescore
  9. 2026-08-15 01:26 UTCEPSS rescore
  10. 2026-08-13 21:57 UTCEPSS rescore
  11. 2026-08-12 13:47 UTCEPSS rescore
  12. 2026-08-08 16:33 UTCEPSS rescore
  13. 2026-08-07 16:23 UTCEPSS rescore
  14. 2026-08-06 13:43 UTCEPSS rescore
  15. 2026-08-06 06:21 UTCOSV refresh
  16. 2026-08-04 15:06 UTCEPSS rescore
  17. 2026-08-03 10:32 UTCEPSS rescore
  18. 2026-08-01 04:12 UTCEPSS rescore
  19. 2026-07-30 16:24 UTCEPSS rescore
  20. 2026-07-30 01:27 UTCEPSS rescore
  21. 2026-07-28 15:32 UTCEPSS rescore
  22. 2026-07-26 14:51 UTCEPSS rescore
  23. 2026-07-25 14:14 UTCEPSS rescore
  24. 2026-07-24 14:14 UTCEPSS rescore
  25. 2026-07-23 14:15 UTCEPSS rescore
  26. 2026-07-23 14:15 UTCEPSS rescore
  27. 2026-07-23 01:47 UTCEG score recompute
  28. 2026-07-22 22:30 UTCEG score recompute
  29. 2026-07-22 14:05 UTCEPSS rescore
  30. 2026-07-21 15:22 UTCEPSS rescore
  31. 2026-07-21 15:22 UTCEPSS rescore
  32. 2026-07-20 21:02 UTCOSV refresh
  33. 2026-07-20 17:04 UTCEPSS rescore
  34. 2026-07-19 14:28 UTCEPSS rescore
  35. 2026-07-19 14:28 UTCEPSS rescore
  36. 2026-07-18 10:02 UTCEPSS rescore
  37. 2026-07-16 16:59 UTCEPSS rescore
  38. 2026-07-16 16:59 UTCEPSS rescore
  39. 2026-07-15 16:55 UTCEPSS rescore
  40. 2026-07-13 22:27 UTCEPSS rescore
  41. 2026-07-13 06:10 UTCEPSS rescore
  42. 2026-07-13 06:10 UTCEPSS rescore
  43. 2026-07-12 05:44 UTCEPSS rescore
  44. 2026-07-11 08:24 UTCEPSS rescore
  45. 2026-07-09 19:06 UTCEPSS rescore
  46. 2026-07-08 15:11 UTCEPSS rescore
  47. 2026-07-06 02:20 UTCEPSS rescore
  48. 2026-07-04 06:28 UTCEPSS rescore
  49. 2026-07-03 16:26 UTCOSV refresh
  50. 2026-07-01 15:03 UTCEPSS rescore
  51. 2026-07-01 15:03 UTCEPSS rescore
  52. 2026-06-29 14:04 UTCEPSS rescore
  53. 2026-06-29 14:04 UTCEPSS rescore
  54. 2026-06-28 04:54 UTCEPSS rescore
  55. 2026-06-28 04:54 UTCEPSS rescore
  56. 2026-06-25 13:47 UTCEPSS rescore
  57. 2026-06-25 13:47 UTCEPSS rescore
  58. 2026-06-24 14:03 UTCEPSS rescore
  59. 2026-06-24 14:03 UTCEPSS rescore
  60. 2026-06-23 21:31 UTCEPSS rescore
  61. 2026-06-23 21:31 UTCEPSS rescore
  62. 2026-06-22 14:23 UTCEPSS rescore
  63. 2026-06-22 14:23 UTCEPSS rescore
  64. 2026-06-21 01:57 UTCEPSS rescore
  65. 2026-06-21 01:57 UTCEPSS rescore
  66. 2026-06-18 17:50 UTCEPSS rescore
  67. 2026-06-18 17:50 UTCEPSS rescore
  68. 2026-06-17 17:50 UTCEPSS rescore
  69. 2026-06-16 17:50 UTCEPSS rescore
  70. 2026-06-15 17:46 UTCEPSS rescore
  71. 2026-06-15 05:13 UTCOSV refresh
  72. 2026-06-14 23:15 UTCEPSS rescore
  73. 2026-06-14 23:15 UTCEPSS rescore
  74. 2026-06-12 23:09 UTCEPSS rescore
  75. 2026-06-12 23:09 UTCEPSS rescore

Publicly available exploits

(2 references)

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

  • GitHub PoCsijiahi/Wordpress_cve-2019-9787_defense
    First seen May 1, 2020

    This is a recurrence of cve-2019-9787 on Wordpress and a hash-based defense.

    Open source ↗
  • GitHub PoCrkatogit/cve-2019-9787_csrf_poc
    First seen Apr 15, 2019
    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2019-9787?
CVE-2019-9787 is a high vulnerability published on March 14, 2019. WordPress before 5.1.1 does not properly filter comment content, leading to Remote Code Execution by unauthenticated users in a default configuration. This occurs because CSRF protection is mishandled, and because Search Engine Optimization of A elements is performed incorrectly, leading to XSS.…
When was CVE-2019-9787 disclosed?
CVE-2019-9787 was first published in the National Vulnerability Database on March 14, 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-9787 actively exploited?
CVE-2019-9787 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39% probability of exploitation in the next 30 days, which ranks it in the top 1.5% of all scored CVEs.
What is the CVSS score of CVE-2019-9787?
CVE-2019-9787 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2019-9787?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-9787, 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-9787

Explore →

Is Your Infrastructure Affected by CVE-2019-9787?

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

Book a Demo →Browse All CVEs