CVE-2026-65553
Unauthenticated RCE in Spider Analyser WordPress plugin (<=2.1.3).
Is CVE-2026-65553 being exploited?
Not confirmed. CVE-2026-65553 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.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-65553?
CVE-2026-65553 is rated Critical with a CVSS score of 10.0. 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-65553?
Yes. A fix has been recorded for CVE-2026-65553. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-65553 affect?
CVE-2026-65553 affects WordPress sites with Spider Analyser plugin <=2.1.3, Self-hosted WordPress, Managed WordPress instances using the plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-65553?
Immediately update/remove Spider Analyser to a patched version (>2.1.3); apply WAF rules and scan for compromise.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote code execution allowing full site takeover, data theft, and lateral movement into internal networks.
Immediate action required
- affected<= 2.1.3
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.