Security readout for executives and security teams
Plain-English summary
CVE-2026-1400 affects the AI Engine WordPress plugin through version 3.3.2. A user with Editor-level access or higher could turn an uploaded image into an executable PHP file on the server. That may allow full site compromise if abused by a malicious or compromised account.
Executive priority
Treat as high priority for WordPress sites using AI Engine, especially if many users have content-editing privileges. Prioritize patching, privilege review, and upload-directory checks. The risk is serious but not currently evidenced as actively exploited in the provided sources.
Technical view
The flaw is CWE-434 arbitrary file upload caused by missing file type validation in rest_helpers_update_media_metadata. The filename parameter in the update_media_metadata endpoint can rename a benign image to a PHP file in uploads. CVSS is 7.2 high: network reachable, low complexity, high privileges required, no user interaction.
Likely exposure
Exposure is limited to WordPress sites running AI Engine up to and including 3.3.2 where attackers have or can obtain Editor-level access or higher. Multi-author sites, agencies, and sites with weak admin hygiene face higher risk.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires authenticated Editor+ privileges, but successful abuse may lead to remote code execution through an executable file in the uploads directory.
Researcher notes
Key evidence comes from Wordfence, CVE records, WordPress plugin source lines, and a WordPress Trac changeset. The bundle identifies affected versions through 3.3.2 but does not name a specific fixed release. Avoid assuming exploit activity without new public evidence.
Mitigation direction
- Update AI Engine to a vendor-fixed version newer than 3.3.2 when available.
- Review and minimize Editor, Administrator, and equivalent privileged WordPress accounts.
- Remove unnecessary or stale privileged accounts immediately.
- Block PHP execution in WordPress uploads directories where operationally safe.
- Monitor uploads directories for unexpected PHP or executable files.
- Check vendor and Wordfence guidance for final fixed-version details.
Validation and detection
- Inventory WordPress sites using AI Engine and record plugin versions.
- Flag any AI Engine installations at version 3.3.2 or earlier.
- Review Editor+ account activity around media uploads and metadata changes.
- Inspect uploads directories for unexpected PHP files or renamed media.
- Confirm deployed plugin code includes the referenced WordPress changeset fix.
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-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell 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-1400 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
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/d5227269-4406-4fcf-af37-f1db0af857d6?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/ai-engine/tags/3.3.0/classes/rest.php#L1104CVE reference
- https://plugins.trac.wordpress.org/changeset/3447500/ai-engine/trunk/classes/rest.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.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.