CVE-2026-16253

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

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

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

The Total Upkeep WordPress plugin before 1.17.3 does not adequately protect the secret that authorizes its backup-restore functionality and exposes it to unauthenticated users, allowing them to disclose sensitive backup information and to force a full site restore that overwrites the live site's files and database.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 12, 2026

Advisory Details (1)

Auto-updated Aug 12, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Total Upkeep (BoldGrid Backup) < 1.17.3 – Unauthenticated Sensitive Data Disclosure and Forced Site Restore via Predictable cron_secret (regression of CVE-2020-36848) | CVE 2026-16253 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/97abf25a-48d4-4dfa-a7a3-de88455be7eb/

Vendor Advisories for CVE-2026-16253(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 / 41× 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 22:21 UTCGHSA enrichment
  3. 2026-08-20 09:14 UTCGHSA enrichment
  4. 2026-08-19 20:06 UTCEG score recompute
  5. 2026-08-19 20:05 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 06:57 UTCGHSA enrichment
  8. 2026-08-18 17:50 UTCEG score recompute
  9. 2026-08-18 17:50 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 04:29 UTCGHSA enrichment
  12. 2026-08-17 15:22 UTCEG score recompute
  13. 2026-08-17 15:22 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 02:14 UTCEG score recompute
  16. 2026-08-17 02:14 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 13:07 UTCEG score recompute
  19. 2026-08-16 13:07 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-16 00:00 UTCGHSA enrichment
  22. 2026-08-15 10:53 UTCEG score recompute
  23. 2026-08-15 10:53 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 21:45 UTCGHSA enrichment
Show 16 more
  1. 2026-08-14 08:38 UTCEG score recompute
  2. 2026-08-14 08:38 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 19:31 UTCGHSA enrichment
  5. 2026-08-13 06:24 UTCEG score recompute
  6. 2026-08-13 06:24 UTCGHSA enrichment
  7. 2026-08-12 17:17 UTCEG score recompute
  8. 2026-08-12 17:17 UTCGHSA enrichment
  9. 2026-08-12 16:21 UTCEG score recompute▲ 7.50
  10. 2026-08-12 16:21 UTCGHSA enrichment
  11. 2026-08-12 16:20 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  12. 2026-08-12 13:50 UTCEPSS rescore
  13. 2026-08-12 06:31 UTCGHSA enrichment
  14. 2026-08-12 06:30 UTCNVD update
  15. 2026-08-12 06:06 UTCEG score recompute
  16. 2026-08-12 06:03 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16253?
CVE-2026-16253 is a high vulnerability published on August 12, 2026. The Total Upkeep WordPress plugin before 1.17.3 does not adequately protect the secret that authorizes its backup-restore functionality and exposes it to unauthenticated users, allowing them to disclose sensitive backup information and to force a full site restore that overwrites the live site's…
When was CVE-2026-16253 disclosed?
CVE-2026-16253 was first published in the National Vulnerability Database on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16253 actively exploited?
CVE-2026-16253 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 79.4% of all scored CVEs.
What is the CVSS score of CVE-2026-16253?
CVE-2026-16253 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-16253?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16253, 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-16253

Explore →

Is Your Infrastructure Affected by CVE-2026-16253?

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

Start Free Scan →Browse All CVEs