CVE-2026-8902: CWE-352 Cross-Site Request Forgery (CSRF) in tierrainnovation AJAX Report Comments
The AJAX Report Comments plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.4. This is due to missing or incorrect nonce validation on the rc_options_page function. This makes it possible for unauthenticated attackers to modify plugin settings including link text and markup, success/failure/already-reported messages, comment threshold, cookie duration, reporter-comment toggle, and notification email address, subject, and message body via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AI Analysis
Technical Summary
CVE-2026-8902 is a CSRF vulnerability in the AJAX Report Comments WordPress plugin (versions up to 2.0.4). The issue arises from missing or incorrect nonce validation on the rc_options_page function, which manages plugin settings. An attacker can exploit this by crafting a forged request that, when executed by an authenticated administrator (e.g., via clicking a link), modifies plugin configuration parameters without authorization. The vulnerability does not impact confidentiality or availability but allows integrity modification of plugin settings. No known exploits are reported in the wild, and no patch or official remediation level has been provided by the vendor.
Potential Impact
An attacker can cause unauthorized changes to plugin settings by exploiting the CSRF vulnerability, potentially altering how the plugin behaves or how notifications are sent. This does not lead to data disclosure or service disruption but can affect the integrity of plugin configuration. The medium CVSS score reflects the limited scope of impact and the requirement for user interaction by an administrator.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should avoid clicking untrusted links while logged into WordPress with administrative privileges and consider disabling or removing the AJAX Report Comments plugin if feasible. Implementing additional CSRF protections at the WordPress or server level may help mitigate risk.
CVE-2026-8902: CWE-352 Cross-Site Request Forgery (CSRF) in tierrainnovation AJAX Report Comments
Description
The AJAX Report Comments plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.4. This is due to missing or incorrect nonce validation on the rc_options_page function. This makes it possible for unauthenticated attackers to modify plugin settings including link text and markup, success/failure/already-reported messages, comment threshold, cookie duration, reporter-comment toggle, and notification email address, subject, and message body via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
CVSS v3.1
Score 4.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-8902 is a CSRF vulnerability in the AJAX Report Comments WordPress plugin (versions up to 2.0.4). The issue arises from missing or incorrect nonce validation on the rc_options_page function, which manages plugin settings. An attacker can exploit this by crafting a forged request that, when executed by an authenticated administrator (e.g., via clicking a link), modifies plugin configuration parameters without authorization. The vulnerability does not impact confidentiality or availability but allows integrity modification of plugin settings. No known exploits are reported in the wild, and no patch or official remediation level has been provided by the vendor.
Potential Impact
An attacker can cause unauthorized changes to plugin settings by exploiting the CSRF vulnerability, potentially altering how the plugin behaves or how notifications are sent. This does not lead to data disclosure or service disruption but can affect the integrity of plugin configuration. The medium CVSS score reflects the limited scope of impact and the requirement for user interaction by an administrator.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should avoid clicking untrusted links while logged into WordPress with administrative privileges and consider disabling or removing the AJAX Report Comments plugin if feasible. Implementing additional CSRF protections at the WordPress or server level may help mitigate risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-05-18T21:16:29.861Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a279b3ce29bf47b5035aa06
Added to database: 6/9/2026, 4:49:00 AM
Last enriched: 6/9/2026, 5:05:32 AM
Last updated: 6/9/2026, 10:56:57 AM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.