Stored XSS via forged plugin settings update
Published May 15, 2025 · Updated May 20, 2025
Cross-site request forgery in aBitGone CommentSafe 1.0.0 and earlier allows remote attackers to store malicious JavaScript in plugin settings. The settings handler at wp-admin/plugins.php?page=abg_commentsafe accepts a forged POST without nonce validation and stores abg_commentsafe_tags without sanitization or output escaping. An authenticated administrator must open attacker-controlled HTML; the saved payload then executes in the WordPress administrative context.
Summary
What happened
Cross-site request forgery in aBitGone CommentSafe 1.0.0 and earlier allows remote attackers to store malicious JavaScript in plugin settings. The settings handler at wp-admin/plugins.php?page=abg_commentsafe accepts a forged POST without nonce validation and stores abg_commentsafe_tags without sanitization or output escaping. An authenticated administrator must open attacker-controlled HTML; the saved payload then executes in the WordPress administrative context.
The record
- CVE
- CVE-2023-7174
- Published
- May 15, 2025
- Updated
- May 20, 2025
- Vendor
- aBitGone
- Product
- CommentSafe
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 15, 2025CVE publishedPublication date reported by the CVE source.
- May 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.0.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- WPScan forged settings POST proof of conceptproof of concept · validated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo