CVE-2026-8902 MEDIUM

CVE-2026-8902: AJAX Report Comments <= 2.0.4 - Cross-Site Request Forgery to Settings Update

Vendor Tierrainnovation
Product AJAX Report Comments
Weakness CWE-352 · CSRF
Published June 9, 2026
Last update June 9, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

AJAX Report Comments versions 2.0.4 and earlier are vulnerable to cross-site request forgery (CSRF). An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the site without their knowledge. The vulnerability requires the victim to visit the attacker's page while authenticated to the WordPress site.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on the site by tricking an authenticated admin into visiting a malicious webpage.

Potential impact on your site

04Site Impact

An attacker can modify site content or settings if they trick an admin into clicking a malicious link while logged in.

Conditions required to exploit

05Prerequisites

The site admin must be logged in and visit a page controlled by the attacker.

Key dates

06Disclosure timeline

June 9, 2026 CVE published
June 9, 2026 Record updated

Related vulnerabilities

08Related CVE