Security readout for executives and security teams
Plain-English summary
CVE-2026-0746 affects the AI Engine WordPress plugin through version 3.3.2. A logged-in low-privilege user could make the website server send requests to other locations. Risk is higher where the plugin’s Public API is enabled and PHP allow_url_fopen is On.
Executive priority
Treat as a near-term WordPress plugin remediation item, especially for public-facing sites with user registration. It is not currently listed as known exploited, but the conditions are common enough to warrant prompt validation and update planning.
Technical view
The issue is authenticated SSRF in AI Engine’s get_audio function. With Subscriber-level access or higher, an attacker can trigger server-originated requests to arbitrary locations. The CVSS 3.1 score is 6.4. Sources state exploitation requires Public API enabled in plugin settings and allow_url_fopen enabled on the server.
Likely exposure
WordPress sites running AI Engine up to and including 3.3.2 are potentially exposed when Public API is enabled and allow_url_fopen is On. Sites allowing public user registration may have more reachable Subscriber-level accounts.
Exploitation context
No provided source or KEV status indicates active exploitation. The vulnerability could be used to reach internal services from the web server’s network position, potentially exposing or changing internal information depending on reachable services.
Researcher notes
Public references identify CWE-918 SSRF and point to the vulnerable chatml.php get_audio code path plus a WordPress.org changeset. The bundle does not provide confirmed exploitation evidence. Avoid assuming exposure unless plugin version, Public API setting, PHP configuration, and authenticated access conditions are verified.
Mitigation direction
- Update AI Engine to a version newer than 3.3.2 if available.
- If no update is available, check current vendor guidance.
- Disable AI Engine Public API if not required.
- Set allow_url_fopen to Off if compatible with site functionality.
- Review and limit Subscriber-level account creation and access.
Validation and detection
- Inventory WordPress sites using the AI Engine plugin.
- Confirm AI Engine version is 3.3.2 or older.
- Check whether AI Engine Public API is enabled.
- Check whether PHP allow_url_fopen is enabled.
- Review logs for unusual authenticated requests to audio-related plugin endpoints.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-0746 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/cbba866d-93dd-4ef5-9670-ab958f61f06e?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/ai-engine/tags/3.3.1/classes/engines/chatml.php#L946CVE reference
- https://plugins.trac.wordpress.org/changeset/3447500/ai-engine/trunk/classes/engines/chatml.phpCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.