CVE-2026-81283
Subscriber PHP Object Injection in WP User Frontend plugin allowing site compromise.
Is CVE-2026-81283 being exploited?
Not confirmed. CVE-2026-81283 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.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-81283?
CVE-2026-81283 is rated High with a CVSS score of 8.8. 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-81283?
Yes. A fix has been recorded for CVE-2026-81283. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-81283 affect?
CVE-2026-81283 affects WP User Frontend plugin <= 4.3.10, WordPress sites with the plugin installed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-81283?
Update WP User Frontend to patched version; disable plugin or restrict subscriber access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated subscriber can trigger PHP Object Injection leading to remote code execution or site takeover.
Immediate action required
- affected<= 4.3.10
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.