CVE-2023-7174: The aBitGone CommentSafe WordPress plugin through 1.0.0 does not have CSRF check in some places, and is missin

Q: How do I fix CVE-2023-7174?

abitgone commentsafe: upgrade to newer than 1.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2023-7174 being exploited?

CVE-2023-7174 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2023-7174 affect?

CVE-2023-7174 affects abitgone commentsafe. Severity is high (CVSS 7.1). 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.

Q: How urgent is CVE-2023-7174?

Priority 32/100. High severity; Public exploit reference

Routine

HIGH 7.1UPGRADE

CVE-2023-7174 is a high-severity flaw (CVSS 7.1) affecting abitgone commentsafe. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 91%)
CISA exploited list	No
Weakness	CWE-352
Published	2025-05-15
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: abitgone

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-05-15 20:15 UTCPublished CVE record published
2026-06-17 06:52 UTCUpdated Record last modified

abitgone abitgone commentsafe UPGRADE

Affected: <= 1.0.0

Fixed in: newer than 1.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy abitgone-commentsafe || rpm -q abitgone-commentsafe || abitgone-commentsafe --version

2. UPGRADE to newer than 1.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade abitgone-commentsafe

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade abitgone-commentsafe

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-7174?

abitgone commentsafe: upgrade to newer than 1.0.0. Exact commands for each OS are on this page.

Is CVE-2023-7174 being exploited?

CVE-2023-7174 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-7174 affect?

CVE-2023-7174 affects abitgone commentsafe. Severity is high (CVSS 7.1). 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.

How urgent is CVE-2023-7174?

Priority 32/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs