Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-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. |
Wed, 11 Jun 2025 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Abitgone
Abitgone abitgone Commentsafe |
|
| Weaknesses | CWE-352 | |
| CPEs | cpe:2.3:a:abitgone:abitgone_commentsafe:*:*:*:*:*:wordpress:*:* | |
| Vendors & Products |
Abitgone
Abitgone abitgone Commentsafe |
Tue, 20 May 2025 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Thu, 15 May 2025 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | aBitGone CommentSafe <= 1.0.0 - Settings Update to Stored XSS via CSRF | |
| References |
|
Status: PUBLISHED
Assigner: WPScan
Published:
Updated: 2025-05-20T15:04:02.535Z
Reserved: 2023-12-29T20:47:02.355Z
Link: CVE-2023-7174
Updated: 2025-05-20T15:03:44.902Z
Status : Analyzed
Published: 2025-05-15T20:15:30.207
Modified: 2025-06-11T19:55:17.260
Link: CVE-2023-7174
No data.
OpenCVE Enrichment
No data.
EUVD