What is the CVSS score of CVE-2026-6639?

CVE-2026-6639 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.4%.

Which versions of AI Copilot WordPress are affected by CVE-2026-6639?

The AI Copilot - Content Generator WordPress plugin (versions 1.4.6 and earlier) allows unauthenticated attackers to steal OpenAI API credentials and access sensitive AI configurations, creating…

How to fix or mitigate CVE-2026-6639?

Within 24 hours: immediately deactivate the AI Copilot - Content Generator plugin and rotate all OpenAI API keys via the OpenAI dashboard; audit OpenAI billing statements and API activity logs for unauthorized usage patterns over the past 30 days. Within 7 days: completely remove the plugin from all WordPress installations, conduct forensic analysis of database backups to document exactly which API keys and configurations were exposed, determine the exposure timeline, and create an incident report for stakeholders. Within 30 days: identify and deploy a replacement WordPress AI plugin that includes proper nonce validation, role-based access controls, and security certification; implement Web Application Firewall (WAF) rules to require authentication for wp-admin/admin-ajax.php endpoints; establish ongoing monitoring of OpenAI API logs and billing alerts for anomalous activity.

AI Copilot WordPress CVE-2026-6639

EUVD-2026-53171 HIGH

Missing Authorization (CWE-862)

2026-08-05 Wordfence

GHSA-8mpj-5qhw-h3qv

PHP WordPress Authentication Bypass Information Disclosure Wordpress Plugin Ai Copilot Content Generator Wupsales

7.5

CVSS 3.1 · Vendor: Wordfence

Severity by source

Vendor (Wordfence) PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

vuln.today AI

7.5 HIGH

Network-accessible unauthenticated AJAX endpoint requires no privileges or interaction; only confidentiality is impacted via API key and config disclosure.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Aug 05, 2026 - 07:47 vuln.today

CVE Published

Aug 05, 2026 - 06:37 cve.org

HIGH 7.5

DescriptionCVE.org

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.

AnalysisAI

Unauthenticated sensitive information exposure in the AI Copilot - Content Generator plugin for WordPress (versions up to and including 1.4.6) allows any remote attacker to retrieve plaintext OpenAI API keys and full AI model configurations. The getCurrentTaskResults() method is exposed via wp_ajax_nopriv_ AJAX hooks with no nonce validation, no authorization checks, and no permission guard - making task results freely accessible to unauthenticated callers. Attackers who enumerate sequential integer task IDs can exfiltrate every stored API key, prompt configuration, and keyword set from the site's database. No active exploitation is confirmed in CISA KEV, and no public exploit code has been identified at time of analysis, though the vulnerability is trivially exploitable given the low attack complexity.

Technical ContextAI

The plugin (CPE: cpe:2.3:a:wupsales:ai_copilot_-_content_generator:*:*:*:*:*:*:*:*) implements a workspace controller pattern where individual methods are selectively protected via getNoncedMethods() and getPermissions(). The getCurrentTaskResults() method in modules/workspace/controller.php:83 was omitted from both protection arrays. Because the base getPermissions() returns an empty array and all AJAX endpoints are registered with WordPress's wp_ajax_nopriv_ hook (frame.php:282), this method is callable by any unauthenticated HTTP client through WordPress's admin-ajax.php dispatcher. The root cause is CWE-862 (Missing Authorization): the developer relied on opt-in protection rather than deny-by-default, leaving a high-sensitivity endpoint unguarded. Task parameters - including the OpenAI API key stored in plaintext per modules/workspace/models/tasks.php:106 - are persisted in the WordPress database and returned verbatim in the JSON response. Task IDs are sequential integers, making brute-force enumeration of all stored task records trivial.

RemediationAI

Update the AI Copilot - Content Generator plugin to any version released after the SVN changeset at https://plugins.trac.wordpress.org/changeset?new=3528734%40ai-copilot-content-generator%2Ftrunk&old=3525474%40ai-copilot-content-generator%2Ftrunk, and verify the installed version exceeds 1.4.6 via the WordPress plugin dashboard. Because the patched release version number is not confirmed from available data, verify the plugin update in the WordPress admin panel before concluding remediation. Immediately rotate any OpenAI API keys that were configured in the plugin on affected sites - assume all API keys stored in task records prior to patching are compromised and must be revoked at https://platform.openai.com/api-keys. As a compensating control prior to patching, site administrators can deactivate the plugin entirely (Settings > Plugins > Deactivate), which removes the AJAX endpoint registration and eliminates the attack surface; however, this disables all plugin functionality. Web application firewall rules blocking requests to admin-ajax.php?action=getCurrentTaskResults can reduce exposure but should not be relied upon as a primary control since action names may vary. Wordfence's threat intelligence entry at https://www.wordfence.com/threat-intel/vulnerabilities/id/247b1921-70a6-4e65-819a-2895bc395e9f?source=cve should be monitored for patch version confirmation.