External risk intelligence

AI Engine WordPress Plugin Sensitive Information Exposure Allows Unauthenticated Token Extraction.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2025-11749

This vulnerability affects a WordPress plugin, which is a type of web application component commonly deployed as public-facing software. The vulnerability exists within a REST API endpoint, a service designed to be network-accessible, making it highly probable that the affected endpoint is reachable from the public internet in typical web server deployments.

Information Disclosure

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory details a critical vulnerability in the AI Engine plugin for WordPress. The issue allows unauthenticated attackers to extract sensitive credentials, potentially enabling them to gain full administrative control of affected WordPress sites. The main concern is confirming relevance and exposure.

Plugin flaw exposes sensitive login tokens.
Gaining admin control affects site integrity.
Confirm if your WordPress sites are impacted.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can exploit this vulnerability by accessing a specific REST API endpoint on a WordPress site where the AI Engine plugin is installed and the "No-Auth URL" feature is enabled. This access allows them to retrieve a 'Bearer Token', which can then be used to impersonate a legitimate user. With this token, an attacker can gain control of a valid session, potentially leading to the creation of a new administrator account and complete compromise of the website.

No authentication required.
Accesses REST API endpoint with token exposure.
Leads to session takeover and privilege escalation.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthenticated attackers to obtain a bearer token from the AI Engine plugin's REST API when the 'No-Auth URL' is enabled. This token may enable attackers to access a valid session, potentially leading to significant impacts on the WordPress site.

Bearer token and session access.
Via a network-accessible API endpoint.
Website control and administrator access.

Operational Fix

Recommended remediation, mitigation, and detection steps

System administrators, application owners, and security teams are responsible for addressing this vulnerability in the AI Engine plugin for WordPress. The first step is to identify all instances of the affected plugin, confirm their reachability and business criticality, and then assign an accountable owner for remediation planning.

Identify affected plugin instances.
Verify exposure and criticality.
Plan remediation with owners.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the AI Engine plugin for WordPress?

AI Engine is a software add-on for WordPress websites that integrates artificial intelligence features directly into the platform. Users typically install this plugin to leverage AI capabilities, such as automated content generation or intelligent chat interfaces, which require the plugin to communicate with external AI services.

What does CWE-200 mean in the context of CVE-2025-11749?

CWE-200 refers to Sensitive Information Exposure. In this specific vulnerability, the plugin fails to protect a 'Bearer Token' that acts like a digital key. Because the software inadvertently reveals this sensitive data through its API, an unauthorized person can capture it and use it to impersonate a legitimate user or administrator.

How does an attacker trigger this vulnerability?

An attacker triggers this by reaching a specific REST API endpoint provided by the plugin. The vulnerability is only active when the 'No-Auth URL' setting is enabled in the plugin configuration. If this specific feature is turned off, the API endpoint is not configured to leak the token, preventing this method of unauthorized access.

Do I need to worry about this if my WordPress site is internal?

Yes, you should still evaluate it. Halo Surface Signal notes that this vulnerability affects a web component typically designed to be network-accessible. While internet-facing sites are at the highest risk, any site with this plugin enabled and the 'No-Auth URL' feature active is susceptible to session takeover if an attacker can reach the site over the network.

What steps should I take if I use the AI Engine plugin?

Start by locating every WordPress site in your environment where the AI Engine plugin is installed. Verify if the 'No-Auth URL' feature is currently enabled, as this is the primary condition for the exposure. Once identified, coordinate with the site owners to review the plugin configuration and proceed with your organization's standard update or remediation process.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.