CVE-2026-1321
WP Restrict Content: unauthenticated escalation via level ID.
Is CVE-2026-1321 being exploited?
Not confirmed. CVE-2026-1321 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.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-1321?
CVE-2026-1321 is rated High with a CVSS score of 8.1. 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-1321?
Yes. A fix has been recorded for CVE-2026-1321. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-1321 affect?
CVE-2026-1321 affects WordPress Membership Plugin – Restrict Content (up to 3.2.20). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-1321?
Upgrade to latest version; validate level IDs and status checks.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated users can register with any membership level (inactive or paid) and gain privileged WordPress roles (e.g., Administrator) via rcp_level.
Patch when possible
- affected<= 3.2.20
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.