CVE-2026-130121: AI Puffer WordPress plugin's AI comment auto-replies let an attacker's comment steer the model into posting stored XSS (removed in 2.5.29)
AI Puffer (gpt3-ai-content-generator, 10,000+ active installs) can auto-reply to WordPress comments with an AI model. Up to and including 2.5.28, insert_comment_reply_logic() saved the model's reply with wp_insert_comment() without the kses filtering WordPress normally applies, so an unauthenticated visitor could write a comment that gets the model to reproduce an HTML/script payload in its reply. The script then runs for every visitor to that page. It only works when an admin set up a Comment Auto-Reply task with 'Action on reply' set to 'Approve' (the default is hold for moderation) and the attacker's comment was approved. Version 2.5.29 (17 November 2026) removed automatic comment replies entirely.
What it is
The vulnerable code is classes/automations/comment-reply-worker.php in the plugin; the fix is changeset 3807151.
This is an indirect prompt injection turned into stored XSS: the attacker never writes HTML into the page directly, the model does, and the plugin trusted model output as safe comment content.
The 2.5.29 changelog: 'Removed automatic comment replies, including their settings and prompts. Old saved tasks and queue items cannot run; posted comments are preserved.' Replies already posted stay on the site.
How to check
- In WP Admin → Plugins, check the AI Puffer version; 2.5.28 or older is affected if a Comment Auto-Reply task with 'Approve' was ever configured.
- Search existing AI-generated comment replies for <script, onerror=, javascript: or iframe.
How to fix
- Update AI Puffer to 2.5.29 or later.
- Review and clean up AI replies already posted, since the update preserves them.
- In general, sanitise LLM output like any untrusted user input (wp_kses_post / escaping) before storing or rendering it.
wp plugin get gpt3-ai-content-generator --field=version
wp db query "SELECT comment_ID, comment_post_ID FROM $(wp db prefix)comments WHERE comment_content REGEXP '<script|onerror=|javascript:|<iframe'"