Skip to main content
VulnerabilityPublished Updated

CVE-2024-32135: Disable Comments | WPZest (WordPress plugin) · SQL Injection

Affects Disable Comments | WPZest (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 7.6 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
WPZest Disable Comments | WPZestAffected
  • <=1.51
Fixed in–

AI-suggested

Until an official fix is released, restrict high-privilege access to the affected plugin and monitor for unusual database activity. Avoid using affected versions of the plugin if possible, or consider disabling the plugin temporarily as a precaution.

Description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WPZest Disable Comments | WPZest.This issue affects Disable Comments | WPZest: from n/a through 1.51.

References

Community reviews

Loading reviews…