AI Copilot WordPress EUVD-2026-53171

The plugin must be installed and active on the WordPress site. At least one task must have been created through a plugin feature such as the Bulk Post Generator - exploitation only yields API keys if tasks exist in the database with OpenAI API key data stored in their parameters. Once that precondition is met, no authentication, no nonce, no session, and no special network positioning are required - any unauthenticated HTTP client on the public internet can call admin-ajax.php with the correct action name. Exploitation is limited by the need to know that the plugin is installed (discoverable via fingerprinting) and requires that task records exist in the database; sites that installed the plugin but never created tasks will expose an empty or error response. The sequential nature of task IDs limits enumeration only by HTTP request rate, not cryptographic secrecy.

The CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) accurately reflects the real-world risk profile for any site that has created tasks while using this plugin. All high-risk CVSS metrics are validated by the description: network accessible, no credentials required, no user interaction, and high confidentiality impact via plaintext API key exposure. The AC:L rating is confirmed - sequential task IDs require no guessing beyond simple integer iteration. EPSS data was not provided in the intelligence feed, preventing quantitative exploitation probability assessment. KEV status is negative, suggesting no confirmed mass exploitation, but this is consistent with a plugin-specific flaw that would be exploited opportunistically rather than broadly. The real-world impact extends beyond the WordPress site itself: a stolen OpenAI API key grants the attacker full API access under the victim's account, enabling financial harm through unauthorized usage, data access, and potential abuse of the victim's AI quotas. The vulnerability is not theoretical - any site that has run the Bulk Post Generator or similar task-creating features and has not patched is actively leaking its API credentials to any unauthenticated caller who knows the plugin is installed.

An attacker scans for WordPress installations with the AI Copilot - Content Generator plugin active (via plugin-specific asset fingerprinting or directory enumeration). The attacker then sends a series of unauthenticated HTTP POST requests to wp-admin/admin-ajax.php with the getCurrentTaskResults action and incrementing integer task IDs (1, 2, 3...). Each successful response returns a JSON object containing the site owner's OpenAI API key in plaintext, along with all AI prompts and model configuration. The attacker uses the recovered API key immediately against OpenAI's API for their own purposes, billing all costs to the victim.