The JS Help Desk WordPress plugin before 3.1.4 does not perform any authorization, nonce, or ownership check on a front-end request dispatcher, allowing unauthenticated users to upload files (limited to the JS Help Desk WordPress plugin before 3.1.4's inert allowed extensions) and attach them to arbitrary users' support tickets.
CVE-2026-14930
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-31. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 15%
- KEV
- Not listed
Published
July 31, 2026
Last Modified
July 31, 2026
Advisory Details (1)
Auto-updated Jul 31, 2026JS Help Desk < 3.1.4 – Unauthenticated Arbitrary Ticket File Attachment Upload | CVE 2026-14930 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/075ca843-e787-43cc-8de4-54d8ddc63d4a/Vendor Advisories for CVE-2026-14930(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 13× in last 7d / 13× 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.
- 2026-08-02 05:54 UTCEG score recompute
- 2026-08-02 05:54 UTCGHSA enrichment
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 18:43 UTCGHSA enrichment
- 2026-08-01 07:32 UTCEG score recompute
- 2026-08-01 07:32 UTCGHSA enrichment
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-31 20:21 UTCEG score recompute▲ 7.50
- 2026-07-31 20:21 UTCGHSA enrichment
- 2026-07-31 20:18 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-07-31 07:24 UTCNVD update
- 2026-07-31 06:30 UTCEG score recompute
- 2026-07-31 06:28 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-14930?
When was CVE-2026-14930 disclosed?
Is CVE-2026-14930 actively exploited?
What is the CVSS score of CVE-2026-14930?
How do I remediate CVE-2026-14930?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-14930
Is Your Infrastructure Affected by CVE-2026-14930?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.