CVE-2026-6639: WordPress AIWU Info Disclosure Flaw

CVE-2026-6639 Overview

CVE-2026-6639 is a sensitive information exposure vulnerability in the AI Chatbot & Workflow Automation by AIWU plugin for WordPress. The flaw affects all versions up to and including 1.4.6. The getCurrentTaskResults() method in modules/workspace/controller.php lacks authentication and authorization checks. Unauthenticated attackers can enumerate sequential task identifiers and retrieve task parameters stored in the database. Exposed data includes plaintext OpenAI API keys, AI prompts, keywords, and full AI model configurations. The issue is classified under [CWE-862: Missing Authorization].

Critical Impact
Unauthenticated attackers can retrieve plaintext OpenAI API keys and confidential AI workflow configurations from any vulnerable WordPress site running the plugin.

Affected Products

AI Chatbot & Workflow Automation by AIWU plugin for WordPress
Plugin slug: ai-copilot-content-generator
All versions up to and including 1.4.6

Discovery Timeline

2026-08-05 - CVE CVE-2026-6639 published to NVD
2026-08-05 - Last updated in NVD database

Technical Details for CVE-2026-6639

Vulnerability Analysis

The vulnerability resides in the workspace controller of the AIWU plugin. The getCurrentTaskResults() method returns task records from the database in a JSON AJAX response without validating the caller's identity or permissions. Task records contain the full parameters supplied when creating jobs through features such as the Bulk Post Generator, including third-party API credentials. An unauthenticated attacker sending sequential task identifiers can enumerate and harvest configuration data across all tenant tasks stored by the plugin.

Root Cause

Three combined defects produce the exposure. First, getCurrentTaskResults() is not registered in the workspace controller's getNoncedMethods() array, so no nonce verification is performed. Second, the base getPermissions() implementation returns an empty array, resulting in no capability check being enforced. Third, all AJAX actions are registered through wp_ajax_nopriv_ hooks at classes/frame.php:282, which explicitly exposes the endpoint to unauthenticated visitors. Sensitive task parameters — including plaintext OpenAI API keys — are then serialized directly into the response.

Attack Vector

Exploitation requires only network access to the target WordPress site. An attacker issues AJAX requests to the plugin's unauthenticated endpoint while iterating a numeric task identifier. Each successful response returns the stored task payload, including the OpenAI API key, prompts, keywords, and model configuration. See the WordPress Plugin Frame Code, WordPress Plugin Controller Code, and WordPress Plugin Tasks Code for the affected source paths. No user interaction, privileges, or authentication tokens are required.

Detection Methods for CVE-2026-6639

Indicators of Compromise

Unauthenticated POST or GET requests to WordPress admin-ajax.php invoking AIWU workspace actions from external IP addresses.
Sequential enumeration patterns targeting task identifier parameters in AJAX requests.
Anomalous OpenAI API usage or billing events originating from IP addresses unrelated to the site's normal operations.
Presence of the ai-copilot-content-generator plugin at version 1.4.6 or earlier.

Detection Strategies

Review WordPress access logs for repeated calls to admin-ajax.php referencing the plugin's workspace controller from unauthenticated sessions.
Correlate outbound traffic and OpenAI account activity to detect abuse of leaked API keys.
Inspect JSON responses served from the plugin endpoint for content containing key material such as sk- prefixed strings.

Monitoring Recommendations

Enable WordPress request logging and forward events to a centralized analytics platform for pattern analysis.
Alert on high-volume requests to admin-ajax.php from a single source enumerating numeric parameters.
Monitor OpenAI usage dashboards for unexpected regions, models, or spikes in token consumption.

How to Mitigate CVE-2026-6639

Immediate Actions Required

Update the AI Chatbot & Workflow Automation by AIWU plugin to a version later than 1.4.6 once the vendor patch is deployed.
Rotate all OpenAI API keys previously stored in plugin tasks, as they must be assumed compromised.
Audit OpenAI billing and usage logs for unauthorized activity across all keys managed through the plugin.
Remove or deactivate the plugin on sites where an upgrade is not immediately feasible.

Patch Information

The vendor has published a fix through the WordPress.org plugin repository. Review the WordPress Plugin Changeset for the specific code changes and the WordPress Plugin Page for the latest release. Additional analysis is available in the Wordfence Vulnerability Report.

Workarounds

Block unauthenticated requests to the plugin's AJAX actions at a Web Application Firewall (WAF) until patching is complete.
Restrict access to admin-ajax.php for the affected action names by IP allowlist where operationally viable.
Temporarily deactivate the plugin and remove stored task records containing sensitive credentials.

bash

# Example WAF rule to block unauthenticated access to the vulnerable AJAX action
# Adjust action name to match the plugin's registered wp_ajax_nopriv_ handler
SecRule REQUEST_URI "@contains /wp-admin/admin-ajax.php" \
  "chain,deny,status:403,id:1026639,msg:'Block AIWU workspace task disclosure (CVE-2026-6639)'"
  SecRule ARGS:action "@rx (?i)aiwu_.*task"