CVE-2026-66668
Subscriber SQL injection in PeepSo Community plugin allowing database tampering
Is CVE-2026-66668 being exploited?
Not confirmed. CVE-2026-66668 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.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-66668?
CVE-2026-66668 is rated High with a CVSS score of 8.5. 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-66668?
Yes. A fix has been recorded for CVE-2026-66668. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-66668 affect?
CVE-2026-66668 affects PeepSo Community plugin <= 9.0.5.2, WordPress sites using PeepSo Community plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-66668?
Update PeepSo Community plugin to a fixed version; restrict subscriber privileges and audit logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Subscriber-level SQL injection enabling database read/modify, data exfiltration and potential account compromise.
Immediate action required
- affected<= 9.0.5.2
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.