Skip to content
Web

CVE-2026-16061

8.6
High
EPSS 0.26%Sep 1, 2026

Unauthenticated SQL injection in Rest Routes WordPress plugin (<=5.5.5).

common questions

Is CVE-2026-16061 being exploited?

Not confirmed. CVE-2026-16061 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.26% probability of exploitation in the next 30 days.

How severe is CVE-2026-16061?

CVE-2026-16061 is rated High with a CVSS score of 8.6. 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-16061?

Not known from our data. No patch reference has been recorded for CVE-2026-16061, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-16061 affect?

CVE-2026-16061 affects Rest Routes WordPress plugin <=5.5.5, WordPress sites using the Rest Routes plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-16061?

Audit sites, disable/remove plugin or apply vendor patch when released; block/monitor REST endpoints.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Rest Routes WordPress plugin <=5.5.5WordPress sites using the Rest Routes plugin
impact

Unauthenticated SQL injection via REST URL allows data exfiltration, DB modification, and potential account takeover.

action required

Immediate action required

affected versions
Unknown Rest Routes
  • affected<= 5.5.5

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free