CVE-2026-18983

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: 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 onedesigns One User Avatar | User Profile Picture versions up to and including 2.5.4 as affected. No release containing a fix is confirmed on record.

The One User Avatar | User Profile Picture plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 2.5.4 via the wpua_action_process_option_update function. This is due to insufficient file type validation in wp_handle_upload() called without a MIME allow-list, with post-write validation relying on the attacker-controlled client-supplied Content-Type header rather than a server-derived type, and no cleanup of files that fail the check. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload files that may be executable, which makes remote code execution possible. in order to exploit this vulnerability an admin has to give subscribers permission to upload avatars. While PHP files and svg files are rejected, dxfp files are accepted.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.7% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.7%
EPSS %ILE
50th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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 total (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)14 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 total (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

August 28, 2026

Last Modified

August 28, 2026

References (6)

Vendor Advisories for CVE-2026-18983(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 18× in last 7d / 95× 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 100 of 166 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. None are among the latest 100 rows. The 66 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18983?
CVE-2026-18983 is a high-severity vulnerability; its CVE record was published on August 28, 2026. The One User Avatar | User Profile Picture plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 2.5.4 via the wpuaactionprocessoptionupdate function. This is due to insufficient file type validation in wphandleupload() called without a MIME…
When was the CVE record for CVE-2026-18983 published?
The CVE record for CVE-2026-18983 was published on August 28, 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 August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-18983 actively exploited?
CVE-2026-18983 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18983?
CVE-2026-18983 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18983?
No fix for CVE-2026-18983 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 onedesigns One User Avatar | User Profile Picture versions up to and including 2.5.4 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-18983 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-18983?

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

Book a Demo →Browse All CVEs