CVE-2026-75798 Overview
CVE-2026-75798 is a missing authorization vulnerability in the AI Engine WordPress plugin versions prior to 3.7.2. The plugin exposes an administration-only feature that relies on a token issued to anonymous visitors instead of a proper authorization check. Unauthenticated attackers can invoke AI queries of their choosing against the site owner's configured provider account. The flaw maps to CWE-862: Missing Authorization and carries a network attack vector with low attack complexity.
Critical Impact
Unauthenticated attackers can consume the site owner's paid AI provider credits and issue arbitrary prompts through the WordPress site.
Affected Products
- AI Engine WordPress plugin versions before 3.7.2
- WordPress sites using AI Engine with a configured AI provider account
- Any deployment exposing the plugin's client-facing AI query endpoint
Discovery Timeline
- 2026-08-26 - CVE-2026-75798 published to NVD
- 2026-08-26 - Last updated in NVD database
Technical Details for CVE-2026-75798
Vulnerability Analysis
The AI Engine plugin integrates generative AI capabilities into WordPress sites, connecting to third-party providers such as OpenAI using credentials configured by the site administrator. One administration-only feature does not enforce a capability or role check on incoming requests. Instead, the plugin issues a token to anonymous visitors and treats possession of that token as sufficient authorization.
An attacker who retrieves this token can invoke the administrative AI query endpoint as if they were the site owner. The provider account bills the site owner for every request, so attackers can drain API credits, submit arbitrary prompts, or use the site as a proxy for AI usage.
Root Cause
The root cause is missing server-side authorization [CWE-862]. The plugin substitutes an anonymous-issued token for a proper current_user_can() capability check. Because the token is handed to unauthenticated visitors by design, it provides no meaningful access control on features intended for administrators.
Attack Vector
Exploitation occurs over the network without authentication or user interaction. An attacker requests the token from the public plugin surface, then submits crafted requests to the AI query endpoint carrying that token. The plugin forwards the prompts to the configured provider using the site owner's API key and returns the response. See the WPScan Vulnerability Report for technical details.
Detection Methods for CVE-2026-75798
Indicators of Compromise
- Unexpected spikes in AI provider API usage or billing from the configured account.
- WordPress access logs showing repeated anonymous requests to AI Engine REST routes under /wp-json/mwai/ or similar plugin endpoints.
- AI provider logs recording prompts unrelated to legitimate site content or workflows.
Detection Strategies
- Review WordPress request logs for unauthenticated calls to AI Engine query endpoints originating from a diverse set of IP addresses.
- Correlate AI provider usage reports with expected site activity to identify unauthorized query volume.
- Enumerate installed AI Engine plugin versions across managed WordPress fleets and flag any release earlier than 3.7.2.
Monitoring Recommendations
- Enable provider-side budget alerts and per-key rate limits on the AI account used by the plugin.
- Forward WordPress and web server logs to a centralized platform and alert on anonymous access patterns to plugin REST routes.
- Track outbound requests from the WordPress host to AI provider endpoints for anomalous volume or timing.
How to Mitigate CVE-2026-75798
Immediate Actions Required
- Upgrade the AI Engine WordPress plugin to version 3.7.2 or later on all affected sites.
- Rotate the AI provider API key configured in the plugin, since it may have been abused before patching.
- Review recent provider billing and usage records for unauthorized activity attributable to the affected site.
Patch Information
The vendor addressed CVE-2026-75798 in AI Engine version 3.7.2 by adding a proper authorization check on the affected administration-only feature. Refer to the WPScan Vulnerability Report for advisory details and confirm the fixed version through the WordPress plugin repository before deploying.
Workarounds
- Disable or uninstall the AI Engine plugin until the patched version can be deployed.
- Restrict access to /wp-json/mwai/ and related plugin REST routes at the web application firewall or reverse proxy layer.
- Apply strict rate limits and spending caps on the AI provider API key used by the plugin to bound potential abuse.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
