CVE-2026-75528

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

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

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-09-02. A secondary CVSS source baseline 7.2; 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.2EG
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.5%CVSS: 7.2Exploit: 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 wpmudev Broken Link Checker versions up to and including 2.4.13 as affected. No release containing a fix is confirmed on record.

The Broken Link Checker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author URL / Link Log in all versions up to, and including, 2.4.13 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires an administrator to perform the plugin's standard dismiss-and-recheck workflow on a link submitted by the attacker via the WordPress comment author URL field, after which the attacker's HTTP server issues a redirect to a URL containing an HTML/JavaScript payload that is stored verbatim in the link log.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
33
EG Risk 33/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)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation0.5% × 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 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.5%
EPSS %ILE
43rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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 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

September 2, 2026

Last Modified

September 2, 2026

References (13)

Vendor Advisories for CVE-2026-75528(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 21× in last 7d / 109× 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 160 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 60 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-75528?
CVE-2026-75528 is a high-severity vulnerability; its CVE record was published on September 2, 2026. The Broken Link Checker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author URL / Link Log in all versions up to, and including, 2.4.13 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject…
When was the CVE record for CVE-2026-75528 published?
The CVE record for CVE-2026-75528 was published on September 2, 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 September 2, 2026; the record at its source may have been updated since.
Is CVE-2026-75528 actively exploited?
CVE-2026-75528 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-75528?
CVE-2026-75528 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-75528?
No fix for CVE-2026-75528 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 wpmudev Broken Link Checker versions up to and including 2.4.13 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-75528 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-75528?

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