CVE-2026-66708
Unauthenticated broken access control in Total Upkeep plugin allows admin-function abuse.
Is CVE-2026-66708 being exploited?
Not confirmed. CVE-2026-66708 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-66708?
CVE-2026-66708 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-66708?
Yes. A fix has been recorded for CVE-2026-66708. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-66708 affect?
CVE-2026-66708 affects Total Upkeep WordPress plugin <=1.17.2, WordPress sites using Total Upkeep. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-66708?
Update Total Upkeep to the latest version or remove the plugin; verify backups and rotate credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can invoke admin-only Total Upkeep functions to read/modify/restore backups, upload files, and potentially achieve site compromise or RCE.
Immediate action required
- affected<= 1.17.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.