CVE-2026-16253 Total Upkeep < 1.17.3 - Unauthenticated Sensitive Data Disclosure and Forced Site Restore via Predictable cron_secret

High 7.5 Published Updated

Unauthenticated attackers can disclose sensitive backup data and force a full site restore by exploiting a predictable cron secret in the Total Upkeep plugin.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-16253?

CVE-2026-16253 is a high-severity vulnerability in Unknown Total Upkeep, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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. This is an incomplete fix of CVE-2020-36848, as the protection added at the time never took effect on distributed copies of the plugin.

Weakness: CWE-200

Which versions are affected by CVE-2026-16253?

How do I fix CVE-2026-16253?

No fix has been published for CVE-2026-16253 yet. Limit exposure of the affected software until one is available.

Is CVE-2026-16253 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16253 exists.

Sources

Also known as GHSA-9629-rv6j-mh73.

Is CVE-2026-16253 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free