AI Copilot Content Generator: Critical Flaw Enables Admin Account (CVE-2026-14526)

Published on 8 August 2026

A single request – and a stranger becomes the administrator of your website. No password, no login, no interaction required. That's exactly what the security vulnerability CVE-2026-14526 in the WordPress plugin AI Copilot – Content Generator enables. Anyone using this plugin should act now – not tomorrow, but today.

The vulnerability was made public on 8 August 2026 and, with a CVSS score of 9.8 out of 10, received the highest criticality rating. For context: anything from 9.0 upwards is classified as "critical." It practically doesn't get any higher. In this article, we explain exactly what happened, how you can check in just a few minutes whether your website is affected, and what concrete steps you need to take right now.

What happened?

The WordPress plugin AI Copilot – Content Generator (vendor: wupsales, plugin slug: ai-copilot-content-generator) contains a serious security vulnerability in all versions up to and including 1.5.6. It allows an attacker without any authentication to create a new user account with administrator privileges. This gives the attacker complete control over the WordPress website – a so-called "full site takeover," meaning the complete takeover.

An administrator account is the highest permission level in WordPress. Whoever holds it can alter content, inject malicious code, create additional users, read out customer data and manipulate the website at will – for example for phishing, sending spam or hiding malware.

The vulnerability was discovered and reported on 7 August 2026 by security researcher d.v4n_s3c (Dinh Van) to the security firm Wordfence. As early as 3 August 2026 – that is, even before the official disclosure – the plugin was pre-emptively removed from the official WordPress.org directory. WordPress.org states:

"This plugin has been closed as of August 3, 2026 and is not available for download. This closure is temporary, pending a full review."

The technical background – explained clearly

The vulnerability belongs to the category "Improper Privilege Management" (CWE-269), i.e. the faulty management of permissions. Specifically, the problem lies in the plugin's so-called workflow controller (in the file modules/workflow/controller.php).

A "workflow" is an automated sequence of actions. For this, the plugin provides an interface (a REST API endpoint – that is, an address through which programs can send commands to the website). This interface accepts an action building block called wp_create_user, which creates a new user – and you can even specify the administrator role in the process. The actual problem: the endpoint does not check whether the requester is even authorised to do so. Anyone can trigger this action.

Now, WordPress has a protective measure called a nonce – a one-time security number code intended to verify a request as legitimate. But this is precisely where the plugin fails twice over: the nonce value (waic-nonce) is output openly in the website's JavaScript code – namely whenever the shortcode [aiwu-form] or the public chatbot is embedded on a publicly visible page. A "shortcode" is a placeholder used to embed functions into a page. The result: any visitor can simply read the security code from the page source code. The protective barrier is thus rendered completely ineffective.

The official CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Translated, this means: the attack is carried out over the network, is technically simple, requires no privileges, no user interaction and has severe impacts on confidentiality, integrity and availability. In short: easy to exploit, maximum damage.

Particularly worrying: according to WPScan, the plugin has a total of 10 vulnerabilities – including another unauthenticated privilege escalation flaw (CVE-2026-2955, likewise CVSS 9.8, fixed in version 1.5.4), SQL injection flaws and further authorisation problems. This points to systemic security problems in the code, rather than a single slip-up.

Who is affected?

Affected are all WordPress websites on which the plugin AI Copilot – Content Generator is installed in a version 1.5.6 or older. At the time of closure, the plugin had around 1,000 active installations according to WPScan/WordPress.org – a manageable number compared to million-install plugins, but existentially threatening for each individual affected operator.

Immediately and acutely at risk are websites on which the shortcode [aiwu-form] or the public chatbot is embedded on a frontend page visible to all. Because that is exactly where the security code becomes publicly readable – making the vulnerability immediately exploitable.

How to check in just a few minutes whether you are affected

1. Find the plugin: Log in to the WordPress admin area and go to Plugins > Installed Plugins. Search for "AI Copilot – Content Generator" or "AIWU".
2. Check the version: If the version displayed is 1.5.6 or lower, your website is affected by CVE-2026-14526.
3. Check the shortcode: Search your pages and posts for [aiwu-form] or a public chatbot. If it is embedded, the vulnerability is immediately exploitable.
4. Review users: Go to Users > All Users and look for unknown administrator accounts. Watch for suspicious patterns such as usernames made of random characters (e.g. "wp_" or "admin_" followed by a cryptic string).
5. Check server logs: Review your web server's access logs for suspicious POST requests to the plugin's workflow endpoints.
6. Use a scanner: Alternatively, use a security scanner such as Wordfence or WPScan (CLI) to automatically detect known vulnerabilities.

What you need to do now

A patch does exist in principle: according to WPScan, the vulnerability is fixed in version 1.5.8, and the version currently listed in the directory is 1.5.9. But beware: since the plugin has been temporarily closed from the WordPress.org directory since 3 August 2026, the update may currently not be available there for automatic download. In its advisory, Wordfence even recommends removing the plugin:

"No known patch available. […] It may be best to uninstall the affected software and find a replacement."

Our concrete recommendation – step by step:

1. Immediate measure: Update the plugin to version 1.5.8 or higher, if available. If no update is accessible via WordPress, deactivate and uninstall the plugin immediately. Given the many additional vulnerabilities, a permanent replacement is the safer choice.
2. Check admin accounts: Immediately delete all unknown or suspicious administrator accounts.
3. Renew passwords and keys: Change the passwords of all existing admin accounts and renew the WordPress security keys (salts) in the wp-config.php file. You can generate new keys via https://api.wordpress.org/secret-key/1.1/salt/. This invalidates all existing sessions – including those of attackers.
4. Remove the shortcode: Remove the [aiwu-form] shortcode and the public chatbot from all frontend pages until a secured update is installed.
5. Enable a WAF: Deploy a Web Application Firewall (a protective filter for web requests) such as Wordfence and set up rules for the workflow endpoint.
6. Analyse logs: Check server logs for signs of compromise – unknown POST requests, new users, altered files.
7. In an emergency: If a compromise is confirmed, take the website offline, create a backup, run a malware scan, change all credentials (WordPress, hosting, database, email) and, if necessary, bring in professional incident response support.

Is the vulnerability already being exploited?

As of 8 August 2026, there are no confirmed reports of active exploitation in the wild. The EPSS score – a value that estimates the probability of exploitation – stands at a moderate 0.612%. But this value is typically low for freshly published vulnerabilities and is likely to rise.

Because the past teaches urgency. Structurally identical vulnerabilities were exploited extremely quickly. The security firm Centripetal AI wrote about the identically constructed vulnerability CVE-2025-27007 in the OttoKit plugin (over 100,000 installations):

"Exploitation was observed just 91 minutes after public disclosure, highlighting the rapid response time of malicious actors."

The security provider Patchstack summarises in its report State of WordPress Security in 2026:

"The weighted median time to first exploit is 5 hours."

In other words: the most heavily targeted vulnerabilities are attacked within hours, not days. Waiting is not an option.

GDPR: Why this is now also a legal matter

For website operators in Germany, CVE-2026-14526 is not only a technical problem but also a data protection issue. If an attacker takes complete control of your website, they can access all the personal data processed there: contact form data, customer data, order data (for WooCommerce shops), newsletter subscribers, comments and more.

This triggers legal obligations:

• Art. 33 GDPR – Notification obligation: In the event of a data breach, you must inform the competent data protection authority within 72 hours of becoming aware of it.
• Art. 34 GDPR – Notification of data subjects: If there is a high risk to the data subjects, they too must be informed.
• Art. 32 GDPR – Technical measures: Controllers are obliged to take appropriate security measures – this includes the timely application of security updates. Anyone who fails to remedy known critical vulnerabilities risks a violation.
• Art. 83 GDPR – Fines: Violations of Art. 32 can be penalised with up to EUR 10 million or 2% of global annual turnover, and more serious violations with up to EUR 20 million or 4%.
• Art. 33(5) GDPR – Documentation: All incidents must be documented internally.

That authorities are serious about this is shown by the Booking.com case: in 2020, the Dutch supervisory authority imposed a fine of EUR 475,000 – solely because of a late notification. And Germany is no sideshow: according to DLA Piper, in 2024 Germany reported the second-highest number of data breaches in Europe, with 27,829 reports.

Context: not an isolated case

The vulnerability fits into a worrying trend. According to Patchstack, a total of 11,334 new vulnerabilities were discovered in the WordPress ecosystem in 2025 – a 42% increase over 2024. 91% of them affected plugins. And alarmingly: 46% of the vulnerabilities had no patch available at the time of publication – exactly the situation we effectively find ourselves in with this plugin.

On top of that: according to Patchstack tests, classic protective solutions such as WAFs or Cloudflare blocked only 26% of all WordPress-specific attacks. Relying on a firewall alone is therefore not enough.

Conclusion

CVE-2026-14526 is a critical vulnerability of the worst kind: unauthenticated, technically trivial to exploit, with complete website takeover as the consequence. Admittedly, the number of installations is manageable at around 1,000, and active mass exploitation has not yet been confirmed – but comparable vulnerabilities were attacked within a matter of hours. To make matters worse, the plugin is currently closed from the official directory and has no fewer than ten vulnerabilities.

Our clear recommendation: Check today whether the plugin AI Copilot – Content Generator is running on your website. If it is, and there is no trustworthy update to version 1.5.8 or higher available, deactivate and uninstall it immediately, check your user accounts and renew passwords and security keys. If there are signs of an actual data breach, the 72-hour GDPR deadline applies. Act now – before an attacker does it for you.