CVE-2026-5436

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-04-08. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-20643 (ENISA EUVD) · GHSA-44gv-5x3q-67mm (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
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: 1.1%CVSS: 8.1Exploit: 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 inc2734 MW WP Form versions up to and including 5.1.1 as affected. No release containing a fix is confirmed on record.

The MW WP Form plugin for WordPress is vulnerable to Arbitrary File Move/Read in all versions up to and including 5.1.1. This is due to insufficient validation of the $name parameter (upload field key) passed to the generate_user_file_dirpath() function, which uses WordPress's path_join() — a function that returns absolute paths unchanged, discarding the intended base directory. The attacker-controlled key is injected via the mwf_upload_files[] POST parameter, which is loaded into the plugin's Data model via _set_request_valiables(). During form processing, regenerate_upload_file_keys() iterates over these keys and calls generate_user_filepath() with the attacker-supplied key as the $name argument — the key survives validation because the targeted file (e.g., wp-config.php) genuinely exists at the absolute path. The _get_attachments() method then re-reads the same surviving keys and passes the resolved file path to move_temp_file_to_upload_dir(), which calls rename() to move the file into the uploads folder. This makes it possible for unauthenticated attackers to move arbitrary files on the server, which can easily lead to remote code execution when the right file is moved (such as wp-config.php). The vulnerability is only exploitable if a file upload field is added to the form and the “Saving inquiry data in database” option is enabled.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 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 within your standard update timelines, and watch for a fix.
EPSS PROB
1.1%
EPSS %ILE
64th
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS. 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a 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

April 8, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated May 6, 2026
No fix on record yet.
Web page

Merge pull request #32 from web-soudan/security/fix-file-upload-path-… · web-soudan/mw-wp-form@f872ab1 · GitHub

https://github.com/web-soudan/mw-wp-form/commit/f872ab18ca670f5867b2241745daa30cd0fab861

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 236 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 136 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-5436?
CVE-2026-5436 is a high-severity vulnerability; its CVE record was published on April 8, 2026. The MW WP Form plugin for WordPress is vulnerable to Arbitrary File Move/Read in all versions up to and including 5.1.1. This is due to insufficient validation of the $name parameter (upload field key) passed to the generateuserfiledirpath() function, which uses WordPress's pathjoin() — a function…
When was the CVE record for CVE-2026-5436 published?
The CVE record for CVE-2026-5436 was published on April 8, 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 24, 2026; the record at its source may have been updated since.
Is CVE-2026-5436 actively exploited?
CVE-2026-5436 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-5436?
CVE-2026-5436 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-5436?
No fix for CVE-2026-5436 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's CNA (Wordfence) lists inc2734 MW WP Form versions up to and including 5.1.1 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-5436?

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

Book a Demo →Browse All CVEs