Vulnerabilities

Vulnerability · CVE-2023-7174

The aBitGone CommentSafe WordPress plugin through 1.0.0 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to mak

Published May 15, 2025 · catalog updated May 20, 2025 · Unknown aBitGone CommentSafe

Check this week

CVE-2023-7174 is not in CISA KEV. FIRST estimates a 19.00% chance of exploitation in the next 30 days. Check whether you run Unknown aBitGone CommentSafe.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
19.00%
Remediation
Vendor / distro source
Affected products
vendor Unknown aBitGone CommentSafe 0 ≤1.0.0

The aBitGone CommentSafe WordPress plugin through 1.0.0 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor Unknown aBitGone CommentSafe 0 ≤1.0.00 ≤1.0.0

How to fix CVE-2023-7174

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2023-7174 is not in CISA KEV. FIRST estimates a 19.00% chance of exploitation in the next 30 days. Check whether you run Unknown aBitGone CommentSafe.

Which versions are affected?

Compare what you have installed with Unknown aBitGone CommentSafe 0 ≤1.0.0 0 ≤1.0.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 19.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 15, 2025 · EUVD

    Detected

    The aBitGone CommentSafe WordPress plugin through 1.0.0 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.

  2. May 20, 2025 · EUVD

    Updated

    The aBitGone CommentSafe WordPress plugin through 1.0.0 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.

Sources

  • CVE.orgVulnerability recordCVE-2023-7174

    Official CVE identifier

    cve.org
  • EUVDVulnerability recordEUVD-2023-59355

    The aBitGone CommentSafe WordPress plugin through 1.0.0 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Oct 17, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.