CVE-2026-52521

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-03. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A SQL injection vulnerability in Z-BlogPHP 1.7.5 allows authenticated attackers to execute arbitrary SQL commands via the id parameter in the CommentBat feature.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

GitHub - LING12138-sg/MyCVE-Report · GitHub

https://github.com/LING12138-sg/MyCVE-Report
generic

GitHub - zblogcn/zblogphp: Z-BlogPHP博客程序 · GitHub

https://github.com/zblogcn/zblogphp

Vendor Advisories for CVE-2026-52521(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 27× in last 7d / 65× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 20:27 UTCGHSA enrichment
  3. 2026-08-20 07:44 UTCGHSA enrichment
  4. 2026-08-19 19:01 UTCEG score recompute
  5. 2026-08-19 19:01 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 04:33 UTCGHSA enrichment
  8. 2026-08-18 15:50 UTCEG score recompute
  9. 2026-08-18 15:50 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 01:22 UTCEG score recompute
  12. 2026-08-18 01:22 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 12:27 UTCGHSA enrichment
  15. 2026-08-16 23:44 UTCEG score recompute
  16. 2026-08-16 23:44 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 11:01 UTCEG score recompute
  19. 2026-08-16 11:01 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 22:18 UTCGHSA enrichment
  22. 2026-08-15 09:35 UTCEG score recompute
  23. 2026-08-15 09:35 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 20:51 UTCGHSA enrichment
Show 40 more
  1. 2026-08-14 08:08 UTCEG score recompute
  2. 2026-08-14 08:08 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 19:25 UTCGHSA enrichment
  5. 2026-08-13 06:42 UTCGHSA enrichment
  6. 2026-08-12 17:59 UTCEG score recompute
  7. 2026-08-12 17:59 UTCGHSA enrichment
  8. 2026-08-12 13:51 UTCEPSS rescore
  9. 2026-08-12 05:16 UTCGHSA enrichment
  10. 2026-08-11 16:33 UTCEG score recompute
  11. 2026-08-11 16:33 UTCGHSA enrichment
  12. 2026-08-11 03:49 UTCEG score recompute
  13. 2026-08-11 03:49 UTCGHSA enrichment
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 15:06 UTCGHSA enrichment
  16. 2026-08-10 02:20 UTCEG score recompute
  17. 2026-08-10 02:20 UTCGHSA enrichment
  18. 2026-08-09 13:46 UTCEPSS rescore
  19. 2026-08-09 13:37 UTCGHSA enrichment
  20. 2026-08-09 00:54 UTCEG score recompute
  21. 2026-08-09 00:54 UTCGHSA enrichment
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-08 12:11 UTCGHSA enrichment
  24. 2026-08-07 23:27 UTCEG score recompute
  25. 2026-08-07 23:27 UTCGHSA enrichment
  26. 2026-08-07 10:44 UTCGHSA enrichment
  27. 2026-08-06 22:00 UTCEG score recompute
  28. 2026-08-06 22:00 UTCGHSA enrichment
  29. 2026-08-06 13:47 UTCEPSS rescore
  30. 2026-08-06 09:17 UTCEG score recompute
  31. 2026-08-06 09:17 UTCGHSA enrichment
  32. 2026-08-05 20:33 UTCGHSA enrichment
  33. 2026-08-05 19:40 UTCEG score recompute▲ 8.10
  34. 2026-08-05 19:40 UTCGHSA enrichment
  35. 2026-08-05 19:40 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-04 15:10 UTCEPSS rescore
  38. 2026-08-03 21:20 UTCNVD update
  39. 2026-08-03 21:08 UTCEG score recompute
  40. 2026-08-03 21:08 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-52521?
CVE-2026-52521 is a high vulnerability published on August 3, 2026. A SQL injection vulnerability in Z-BlogPHP 1.7.5 allows authenticated attackers to execute arbitrary SQL commands via the id parameter in the CommentBat feature.
When was CVE-2026-52521 disclosed?
CVE-2026-52521 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52521 actively exploited?
CVE-2026-52521 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.9% of all scored CVEs.
What is the CVSS score of CVE-2026-52521?
CVE-2026-52521 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-52521?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52521, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-52521?

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

Start Free Scan →Browse All CVEs