CVE-2021-39343

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 1.0% (63rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.8 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2022-05-24) is not newer than that change (2025-04-25), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
5.5EG
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: 1.0%CVSS: 5.5Exploit: None knownExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2021 — if the vendor still supports the product, apply the fixed version it names; if not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

The CVE record's CNA (Wordfence) lists MPL-Publisher versions 1.30.2 up to and including 1.30.2 as affected. No release containing a fix is confirmed on record.

The MPL-Publisher WordPress plugin is vulnerable to Stored Cross-Site Scripting due to insufficient input validation and sanitization via several parameters found in the ~/libs/PublisherController.php file which allowed attackers with administrative user access to inject arbitrary web scripts, in versions up to and including 1.30.2. This affects multi-site installations where unfiltered_html is disabled for administrators, and sites where unfiltered_html is disabled.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.0% × 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 has been recorded since the CVE record was published in 2021. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
1.0%
EPSS %ILE
63rd
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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 has been recorded since the CVE record was published in 2021. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

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

October 19, 2021

Last Modified

April 25, 2025

References (3)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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 94 of 194 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2021-39343?
CVE-2021-39343 is a medium-severity vulnerability; its CVE record was published on October 19, 2021. The MPL-Publisher WordPress plugin is vulnerable to Stored Cross-Site Scripting due to insufficient input validation and sanitization via several parameters found in the ~/libs/PublisherController.php file which allowed attackers with administrative user access to inject arbitrary web scripts, in…
When was CVE-2021-39343 made public?
CVE-2021-39343 was made public on October 15, 2021: that is the date its CVE record's CNA, Wordfence, gives for when the vulnerability was made public. The CVE record itself was published on October 19, 2021. EchelonGraph's copy of the record carries a last-modified date of April 25, 2025; the record at its source may have been updated since.
Is CVE-2021-39343 actively exploited?
CVE-2021-39343 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (63rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-39343?
CVE-2021-39343 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2021-39343?
No fix for CVE-2021-39343 has been recorded since its CVE record was published in 2021. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product. The CVE record's CNA (Wordfence) lists MPL-Publisher versions 1.30.2 up to and including 1.30.2 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2021-39343

Explore →

Is Your Infrastructure Affected by CVE-2021-39343?

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