AI Puffer <= 2.4.89 - Missing Authorization to Authenticated (Subscriber+) Global Plugin Settings Modification via ajax_save_cpt_indexing_options AJAX Endpoint
Strategic Overview
- Status
- Patched in 2.4.90
- Affected Plugin
- AI Puffer – MCP, AI Chatbot & Content Automation
- Affected Version
<= 2.4.89- CVSS
- 3.1Low
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-104741
At a glance
CVE-2026-104741 is a low-severity Missing Authorization vulnerability in the AI Puffer WordPress plugin, affecting versions <= 2.4.89. It carries a CVSS score of 3.1 (reachable over the network). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.4.90; sites on affected versions should update now. Disclosed October 2026, reported by Wordfence PRISM.
Vulnerability Overview
The AI Puffer – Chat. Create. Automate. (formerly AI Power) plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.4.89. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to modify global plugin indexing and vector-search configuration options (aipkit_training_general_settings and aipkit_indexing_field_settings), including chunking parameters, file upload visibility, and per-CPT field indexing settings, affecting all users of the plugin. This is only exploitable in configurations where an administrator has granted 'sources' module access to a lower-privileged role via the plugin's Role Manager.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.
CWE-862: Missing Authorization
AI Puffer <= 2.4.89 carries this weakness at sources, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For AI Puffer the fix is 2.4.90: builds <= 2.4.89 are affected, anything from 2.4.90 onward is not.
Remediation
Update to version 2.4.90, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: AI Puffer 2.4.90 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 8.1CVE-2023-0405: GPT AI Power <= 1.4.37 Missing Authorization
CVE-2023-0405 - 6.3CVE-2024-13361: AI Power Authenticated (Subscriber+) Arbitrary
CVE-2024-13361 - 5.3CVE-2023-51527: AI Power: Complete AI Pack Sensitive Data Exposure
CVE-2023-51527 - 3.1CVE-2026-104742: AI Puffer Authenticated (Subscriber+) Semantic
CVE-2026-104742
Other vulnerabilities in AI Puffer – MCP, AI Chatbot & Content Automation
- 9.8CVE-2024-10392: AI Power: Complete AI Pack Arbitrary File Upload
CVE-2024-10392 - 7.2CVE-2025-0428: AI Power: Complete AI Pack PHP Object Injection
CVE-2025-0428 - 7.2CVE-2025-0429: AI Power: Complete AI Pack PHP Object Injection
CVE-2025-0429 - 6.4CVE-2024-37465: GPT3 AI Content Writer <= 1.8.66 Stored XSS
CVE-2024-37465 - 6.1CVE-2024-13362: Freemius <= 2.10.1 Reflected DOM-Based XSS
CVE-2024-13362 - 6.1CVE-2023-33999: Freemius SDK <= 2.5.9 Reflected Cross-Site Scripting
CVE-2023-33999 - 5.4CVE-2024-13360: AI Power: Complete AI Pack <= 1.8.96 SSRF
CVE-2024-13360 - 4.3CVE-2025-47470: GPT3 AI Content Writer <= 1.9.14 CSRF
CVE-2025-47470
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C