CVE-2026-65556
Unauthenticated PHP object injection in WPBruiser allowing site takeover.
Is CVE-2026-65556 being exploited?
Not confirmed. CVE-2026-65556 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.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-65556?
CVE-2026-65556 is rated Critical with a CVSS score of 9.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-65556?
Yes. A fix has been recorded for CVE-2026-65556. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-65556 affect?
CVE-2026-65556 affects WPBruiser {no- Captcha anti-Spam} <= 3.1.43, WordPress sites running the plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-65556?
Update WPBruiser to fixed version (>3.1.43) or remove plugin; audit and restore from clean backups.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated PHP object injection enabling remote code execution and full site takeover via PHP deserialization on vulnerable WordPress sites.
Immediate action required
- affected<= 3.1.43
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.