Ai Engine - Security Vulnerability (CVE-2026-96561)

CVE-2026-96561

Vulnerability CVE-2026-96561 CWE-1427 PLUGIN ai-engine HIGH

The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 3.8.0 This is due to a chain of missing input neutralization and output escaping across the /mwai-ui/v1/chats/submit REST endpoint, the PHP error-log parser (MeowKit_MWAI_Helpers::php_error_logs), the Advisor task (Meow_MWAI_Modules_Advisor::run_advisor), and the Advisor dashboard widget (advisor_metabox): the server-parameter denylist in chat_submit strips only exact key names such as 'model' while convert_keys() later canonicalizes 'model_' back to 'model', allowing an unauthenticated caller to place an attacker-controlled string (including CR/LF) into $query->model; final_checks() throws an Exception whose message embeds that raw string, and the non-streaming, non-admin catch branch writes it to the PHP error log unmodified — creating a forged log line that the plugin's own parser subsequently returns as recent PHP-error content; run_advisor() then appends that content verbatim to the AI prompt (indirect prompt injection — CWE-1427), the returned JSON is stored in the mwai_advisor_data option with no schema validation or HTML sanitization, and advisor_metabox() concatenates the resulting 'title' and 'description' values directly into the WordPress dashboard widget without esc_html(), wp_kses(), or equivalent escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator accesses the WordPress dashboard.

CVE-2026-96561

HIGH CVSS 7.2 Published 2026-10-01 Updated 2026-10-01

AI Risk Elevated (72/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority

Severity Band HIGH

CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Affected Components 2

Reference Links 10

AI Risk Engine Elevated (72/100)

Exploitability Medium

Active Exploitation No strong signal

Published Exploit Status No public exploit references

Threat Timeline

2026-10-01 CVE published and first recorded in the threat feed.
2026-10-01 Record updated with latest vulnerability metadata.
2026-10-01 AI technical context refreshed for mitigation and impact guidance.
Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 6 days ago

AI enriched 6 days ago (2026-10-01 18:41 UTC)

Technical Summary

Potential Impact

Severity is HIGH (CVSS 7.2). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Medium based on low-bar exploit prerequisites.

Primary risk drivers: low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 72/100 (Elevated, Medium) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Ai Engine PLUGIN · ai-engine Affected range not specified Fixed version not specified

for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to PLUGIN · for-wordpress-is-vulnerable-to-stored-cross-site-scripting-in-versions-up-to Affected range not specified Fixed version not specified

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update Ai Engine to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Ai Engine, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Ai Engine. No account is needed to exploit this, so a public site is reachable by anyone.

How do I fix it?

Update Ai Engine to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Cross-Site Scripting (XSS) flaw. An attacker who exploits it can run script in a visitor's browser, stealing sessions or planting an administrator account.