WordPress plugin
Comments Evolved for WordPress security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium1
- Low0
All Comments Evolved for WordPress vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.4 | Authenticated (Administrator+) Stored Cross-Site Scripting ≤1.6.3No patch available | CVE-2024-34420 |
- Medium4.4Authenticated (Administrator+) Stored Cross-Site Scripting
≤1.6.3No patch available
Comments Evolved for WordPress: common questions
Does Comments Evolved for WordPress have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Comments Evolved for WordPress: 1 medium. At least one is not fixed in the latest version.
How do I check which version of Comments Evolved for WordPress I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Comments Evolved for WordPress vulnerability?
CVE-2024-34420, published May 6, 2024: Comments Evolved for WordPress <= 1.6.3 - Authenticated (Administrator+) Stored Cross-Site Scripting. Severity: Medium (CVSS 4.4).
Is any Comments Evolved for WordPress vulnerability listed in CISA KEV?
No. None of the known Comments Evolved for WordPress vulnerabilities is currently listed in the CISA KEV catalog.