Quick answers
- Is CVE-2026-96327 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96327 being exploited in the wild.
- How severe is CVE-2026-96327?
- Critical severity, with a CVSS score of 9.3, published 9 October 2026.
- Which products and versions are affected?
- Vibethemes WPLMS before 1.9.9.8.2.
- Is there a fix for CVE-2026-96327?
- Yes: fixed in 1.9.9.8.2. Until then: If unable to update immediately, use a Web Application Firewall (WAF) rule or security plugin like Patchstack to block SQL injection attempts targeting the vulnerable plugin until patching is completed. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-96327 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-96327?
- Check whether you run Vibethemes WPLMS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.9.9.8.2
If unable to update immediately, use a Web Application Firewall (WAF) rule or security plugin like Patchstack to block SQL injection attempts targeting the vulnerable plugin until patching is completed.
Technical details
An improper neutralization of SQL metacharacters in the wplms_plugin allows blind SQL injection without authentication. The vulnerability permits attackers to execute arbitrary SQL queries against the WordPress database through a network attack vector. A patch is available in version 1.9.9.8.2 and later.
Affected products
- VibeThemes WPLMS before 1.9.9.8.2
Timeline
- 2026-09-05: disclosed
- 2026-10-02: advisory
- 2026-10-02: patched