CVE-2026-0746 MEDIUM

CVE-2026-0746: AI Engine <= 3.3.2 - Authenticated (Subscriber+) Server-Side Request Forgery

Vendor Tigroumeow
Product AI Engine – The Chatbot, AI Framework & MCP for WordPress
Weakness CWE-918 · SSRF
Published January 27, 2026
Last update April 8, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

The AI Engine plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.3.2 via the 'get_audio' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services, if "Public API" is enabled in the plugin settings, and 'allow_url_fopen' is set to 'On' on the server.

Explanation of Vulnerability in Simple Terms

02Summary

The AI Engine plugin for WordPress contains a server-side request forgery (SSRF) vulnerability that allows authenticated users to make the site send HTTP requests to internal or external systems on the attacker's behalf. An attacker with low-level WordPress access can exploit this to access internal services, retrieve sensitive data, or interact with external systems. The vulnerability affects versions up to 3.3.2.

What an attacker can do

03Attacker Capabilities

Make your site send HTTP requests to internal networks or external systems to retrieve data or perform actions.

Potential impact on your site

04Site Impact

Attackers with basic WordPress access can probe your internal network, access cloud metadata services, or interact with external APIs on your site's behalf.

Conditions required to exploit

05Prerequisites

Attacker needs a low-privilege WordPress user account (subscriber or higher); no user interaction required.

Key dates

06Disclosure timeline

January 27, 2026 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE