WordPress plugin
WP-RecentComments 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.
- Critical1
- High0
- Medium2
- Low0
All WP-RecentComments vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium5.3 | Unauthenticated Information Exposure ≤2.2.7No patch available | CVE-2023-23886 | |
| Medium6.1 | Cross-Site Scripting <2.0.7Update to 2.0.7 | CVE-2012-1068 | |
| Critical9.8 | SQL Injection ≤2.0.7Update to 2.1 | CVE-2012-1067 |
- Medium5.3Unauthenticated Information Exposure
≤2.2.7No patch available
- Medium6.1Cross-Site Scripting
<2.0.7Update to 2.0.7
- Critical9.8SQL Injection
≤2.0.7Update to 2.1
WP-RecentComments: common questions
Does WP-RecentComments have known vulnerabilities?
Yes. VulnCrest Radar lists 3 known vulnerabilities in WP-RecentComments: 1 critical, 2 medium. At least one is not fixed in the latest version.
How do I check which version of WP-RecentComments 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 WP-RecentComments vulnerability?
CVE-2023-23886, published Feb 22, 2023: WP-RecentComments <= 2.2.7 - Unauthenticated Information Exposure. Severity: Medium (CVSS 5.3).
Is any WP-RecentComments vulnerability listed in CISA KEV?
No. None of the known WP-RecentComments vulnerabilities is currently listed in the CISA KEV catalog.