CVE-2026-9626

MEDIUMPre-NVD 6.46.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.4 from GitHub Security Advisory published 2026-07-03. A secondary CVSS source baseline 6.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-41490 (ENISA EUVD) · GHSA-4689-rgvq-62r3 (GitHub Security Advisories)Source: ENISA EUVD

6.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.4Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (Wordfence) lists parorrey JSON API User versions up to and including 4.1.0 as affected. No release containing a fix is confirmed on record.

The JSON API User plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'content' parameter of the post_comment API endpoint in versions up to, and including, 4.1.0 This is due to insufficient input sanitization in the post_comment() function, which passes the attacker-controlled comment_content value directly to wp_insert_comment() without applying any HTML sanitization, and additionally allows the caller to set comment_approved=1 to self-approve the comment and bypass moderation. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

CVSS v3
6.4
EG Score
6.4MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity64% × 45%
Impact severity (EG Severity): CVSS 6.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.4): severity, escalated by confirmed exploitation. This CVE's 6.4 is its impact severity (EG Severity), not escalated.

EG Severity
6.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 3, 2026

Last Modified

July 6, 2026

Vendor Advisories for CVE-2026-9626(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 219 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-9626?
CVE-2026-9626 is a medium-severity vulnerability; its CVE record was published on July 3, 2026. The JSON API User plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'content' parameter of the postcomment API endpoint in versions up to, and including, 4.1.0 This is due to insufficient input sanitization in the postcomment() function, which passes the attacker-controlled…
When was the CVE record for CVE-2026-9626 published?
The CVE record for CVE-2026-9626 was published on July 3, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 6, 2026; the record at its source may have been updated since.
Is CVE-2026-9626 actively exploited?
CVE-2026-9626 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9626?
CVE-2026-9626 has a CVSS base score of 6.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-9626?
No fix for CVE-2026-9626 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Wordfence) lists parorrey JSON API User versions up to and including 4.1.0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-9626 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9626

Explore →

Is Your Infrastructure Affected by CVE-2026-9626?

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