WordPress plugin
aBitGone CommentSafe 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 aBitGone CommentSafe vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Cross-Site Request Forgery to Settings Update and Cross-Site Request Forgery ≤1.0.0No patch available | CVE-2023-7174 |
- Medium6.1Cross-Site Request Forgery to Settings Update and Cross-Site Request Forgery
≤1.0.0No patch available
aBitGone CommentSafe: common questions
Does aBitGone CommentSafe have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in aBitGone CommentSafe: 1 medium. At least one is not fixed in the latest version.
How do I check which version of aBitGone CommentSafe 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 aBitGone CommentSafe vulnerability?
CVE-2023-7174, published Jan 23, 2024: aBitGone CommentSafe <= 1.0.0 - Cross-Site Request Forgery to Settings Update and Cross-Site Request Forgery. Severity: Medium (CVSS 6.1).
Is any aBitGone CommentSafe vulnerability listed in CISA KEV?
No. None of the known aBitGone CommentSafe vulnerabilities is currently listed in the CISA KEV catalog.