CVE-2026-6639 in AI Chatbot & Workflow Automation Plugin
Summary
by MITRE • 08/05/2026
The AI Chatbot & Workflow Automation by AIWU plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.4.6. This is due to the `getCurrentTaskResults()` method in `modules/workspace/controller.php` being accessible without authentication or authorization checks. The method is not included in the workspace controller's `getNoncedMethods()` array, the base `getPermissions()` returns an empty array, and all AJAX actions are registered with `wp_ajax_nopriv_` hooks (`classes/frame.php:282`). When tasks are created via features like the Bulk Post Generator, the task parameters — including the OpenAI API key in plaintext, AI prompts, keywords, and full AI model configuration — are stored in the database and returned in the JSON response. This makes it possible for unauthenticated attackers to enumerate sequential task IDs and retrieve sensitive configuration data including API keys.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 08/05/2026
The vulnerability identified in the AI Chatbot & Workflow Automation plugin for WordPress represents a critical sensitive information exposure flaw that undermines the security posture of affected systems. This weakness stems from inadequate authentication and authorization controls within the plugin's architecture, specifically targeting the `getCurrentTaskResults()` method which serves as an entry point for unauthorized data retrieval. The vulnerability affects all versions up to and including 1.4.6, making it a widespread concern across numerous installations that have not yet received updates.
The technical implementation of this flaw manifests through multiple design weaknesses within the plugin's access control mechanisms. The `getCurrentTaskResults()` method fails to undergo proper authentication verification as it is not included in the workspace controller's `getNoncedMethods()` array, which serves as a critical security gatekeeper for method execution. Additionally, the base `getPermissions()` method returns an empty array, effectively removing any permission validation layer that might otherwise protect sensitive operations. The registration of all AJAX actions with `wp_ajax_nopriv_` hooks further compounds this issue by allowing completely unauthenticated access to the vulnerable functionality, as these hooks bypass standard WordPress authentication requirements and directly expose backend methods to public access.
The operational impact of this vulnerability extends beyond simple data exposure, creating a comprehensive risk landscape for affected WordPress installations. When users create tasks through various features such as the Bulk Post Generator, the system stores sensitive configuration parameters in plaintext within the database, including OpenAI API keys, AI prompts, keywords, and complete model configurations. This storage pattern creates a persistent repository of credentials and system information that becomes accessible to any attacker capable of enumerating sequential task IDs. The vulnerability enables attackers to systematically discover and retrieve these stored credentials, potentially gaining access to cloud-based AI services and compromising the confidentiality of user-generated content and system configurations.
This security weakness aligns with several established cybersecurity frameworks and threat modeling approaches, particularly CWE-200 which addresses "Information Exposure" and CWE-306 which covers "Missing Authentication for Critical Functionality." The vulnerability also maps to ATT&CK technique T1528 - "Steal Application Access Token," as it enables unauthorized access to application-specific credentials through the exposure of stored API keys. Furthermore, this issue demonstrates characteristics of privilege escalation through insufficient access controls, similar to ATT&CK's T1078 - "Valid Accounts" where attackers leverage exposed credentials to gain deeper system access.
Mitigation strategies for this vulnerability should focus on immediate remediation through plugin updates to versions that address the authentication gaps. Administrators must ensure that all affected installations receive patches that properly implement nonce validation and authentication checks for the `getCurrentTaskResults()` method. Additionally, security hardening measures including regular monitoring of AJAX endpoint access patterns, implementation of rate limiting for API calls, and comprehensive review of stored credential management practices should be implemented. Organizations should also consider implementing database-level access controls to limit exposure of sensitive configuration data and establish regular audits of stored credentials to detect potential unauthorized access attempts. The vulnerability serves as a reminder of the critical importance of proper authentication implementation in web applications, particularly when dealing with systems that handle third-party API keys and sensitive operational parameters.