CVE-2026-14929

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-07-31. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: Elevated riskExposed: 0

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

The JS Help Desk WordPress plugin before 3.1.4 does not verify ownership of the targeted reply before updating it, allowing any authenticated user (Subscriber and above) to overwrite the content of any support-ticket reply on the site.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
35(Track)
EG Risk 35/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
Severity43% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

July 31, 2026

Last Modified

July 31, 2026

Advisory Details (1)

Auto-updated Jul 31, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

JS Help Desk < 3.1.4 – Subscriber+ Ticket Reply Modification via IDOR | CVE 2026-14929 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/2d786e43-6dbc-4d63-844e-2ca1384cdfd3/

Vendor Advisories for CVE-2026-14929(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 20× in last 7d / 64× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 16:00 UTCEG score recompute
  3. 2026-08-20 16:00 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 15:58 UTCGHSA enrichment
  6. 2026-08-18 15:51 UTCEG score recompute
  7. 2026-08-18 15:51 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 14:38 UTCEG score recompute
  10. 2026-08-17 14:38 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 14:37 UTCEG score recompute
  14. 2026-08-16 14:37 UTCGHSA enrichment
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 14:36 UTCEG score recompute
  17. 2026-08-15 14:36 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 14:35 UTCEG score recompute
  20. 2026-08-14 14:35 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 14:34 UTCGHSA enrichment
  23. 2026-08-12 14:34 UTCEG score recompute
  24. 2026-08-12 14:34 UTCGHSA enrichment
  25. 2026-08-12 13:50 UTCEPSS rescore
Show 39 more
  1. 2026-08-11 14:33 UTCEG score recompute
  2. 2026-08-11 14:33 UTCGHSA enrichment
  3. 2026-08-11 13:42 UTCEPSS rescore
  4. 2026-08-10 23:59 UTCEPSS rescore
  5. 2026-08-10 14:32 UTCGHSA enrichment
  6. 2026-08-09 14:30 UTCEG score recompute
  7. 2026-08-09 14:30 UTCGHSA enrichment
  8. 2026-08-09 13:46 UTCEPSS rescore
  9. 2026-08-08 16:37 UTCEPSS rescore
  10. 2026-08-08 14:30 UTCEG score recompute
  11. 2026-08-08 14:30 UTCGHSA enrichment
  12. 2026-08-07 14:29 UTCGHSA enrichment
  13. 2026-08-06 14:29 UTCEG score recompute
  14. 2026-08-06 14:29 UTCGHSA enrichment
  15. 2026-08-06 13:46 UTCEPSS rescore
  16. 2026-08-05 19:17 UTCEPSS rescore
  17. 2026-08-05 14:28 UTCEG score recompute
  18. 2026-08-05 14:28 UTCGHSA enrichment
  19. 2026-08-04 15:09 UTCEPSS rescore
  20. 2026-08-04 14:26 UTCEG score recompute
  21. 2026-08-04 14:26 UTCGHSA enrichment
  22. 2026-08-04 10:38 UTCEPSS rescore
  23. 2026-08-03 14:26 UTCEG score recompute
  24. 2026-08-03 14:26 UTCGHSA enrichment
  25. 2026-08-03 10:35 UTCEPSS rescore
  26. 2026-08-02 14:25 UTCEG score recompute
  27. 2026-08-02 14:25 UTCGHSA enrichment
  28. 2026-08-02 02:26 UTCEPSS rescore
  29. 2026-08-01 14:25 UTCEG score recompute
  30. 2026-08-01 14:25 UTCGHSA enrichment
  31. 2026-08-01 04:15 UTCEPSS rescore
  32. 2026-07-31 14:24 UTCEG score recompute
  33. 2026-07-31 14:24 UTCGHSA enrichment
  34. 2026-07-31 13:59 UTCEG score recompute▲ 4.30
  35. 2026-07-31 13:59 UTCGHSA enrichment
  36. 2026-07-31 13:58 UTCMITRE cvelistV5CVSS v3 → 4.3 · severity → MEDIUM
  37. 2026-07-31 07:24 UTCNVD update
  38. 2026-07-31 06:30 UTCEG score recompute
  39. 2026-07-31 06:28 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-14929?
CVE-2026-14929 is a medium vulnerability published on July 31, 2026. The JS Help Desk WordPress plugin before 3.1.4 does not verify ownership of the targeted reply before updating it, allowing any authenticated user (Subscriber and above) to overwrite the content of any support-ticket reply on the site.
When was CVE-2026-14929 disclosed?
CVE-2026-14929 was first published in the National Vulnerability Database on July 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14929 actively exploited?
CVE-2026-14929 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.1% of all scored CVEs.
What is the CVSS score of CVE-2026-14929?
CVE-2026-14929 has a CVSS v3.1 base score of 4.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-14929?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14929, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-14929?

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

Start Free Scan →Browse All CVEs