Skip to main content
VulnerabilityPublished

CVE-2026-7385: Decent Comments (WordPress plugin) · Information Exposure

Affects Decent Comments (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.8 Medium : upgrade to 3.0.2 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.0.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 17 Nov 2026.

What to do

Upgrade Decent Comments (WordPress plugin) to 3.0.2.

Affected software

ProductAffectedFixed in
Decent CommentsAffected
  • <3.0.2
Fixed in
  • 3.0.2

AI-suggested

If you cannot patch yet, consider restricting access to the REST API endpoint through web server or WordPress configuration to limit exposure of email addresses.

Description

The Decent Comments WordPress plugin before 3.0.2 does not restrict access to comment author email addresses and post author email addresses via its REST API endpoint, allowing unauthenticated attackers to enumerate registered user email addresses.

References

Community reviews

Loading reviews…