WordPress plugin
Verification Code for Comments 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 Verification Code for Comments vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium5.3 | Reflected Cross-Site Scripting ≤2.1.0No patch available | CVE-2014-4565 |
- Medium5.3Reflected Cross-Site Scripting
≤2.1.0No patch available
Verification Code for Comments: common questions
Does Verification Code for Comments have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Verification Code for Comments: 1 medium. At least one is not fixed in the latest version.
How do I check which version of Verification Code for Comments 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 Verification Code for Comments vulnerability?
CVE-2014-4565, published Aug 1, 2014: Verification Code for Comments <= 2.1.0 - Reflected Cross-Site Scripting. Severity: Medium (CVSS 5.3).
Is any Verification Code for Comments vulnerability listed in CISA KEV?
No. None of the known Verification Code for Comments vulnerabilities is currently listed in the CISA KEV catalog.