CVE-2026-96327
Blind SQL injection in WPLMS WordPress plugin allows database extraction.
Is CVE-2026-96327 being exploited?
Not confirmed. CVE-2026-96327 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.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-96327?
CVE-2026-96327 is rated Critical with a CVSS score of 9.3. 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-96327?
Yes. A fix has been recorded for CVE-2026-96327. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-96327 affect?
CVE-2026-96327 affects VibeThemes WPLMS WordPress plugin < 1.9.9.8.2, WordPress sites running WPLMS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-96327?
Update WPLMS to 1.9.9.8.2+, rotate credentials, review logs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote blind SQL injection via plugin input allowing attackers to enumerate/exfiltrate DB data, steal credentials, and potentially compromise sites.
Immediate action required
- affected< 1.9.9.8.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.