Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as high-privilege user
-
DeliveryAccess file upload functionality
-
ExploitUpload malicious PHP/shell file
-
ExecutionExecute uploaded web shell
-
ImpactAchieve remote code execution on server
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK
2 techniques across 2 tactics: Command and Control, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires high-privilege authenticated access (administrator role) to Jordy Meow Photo Engine versions <= 6.4.9. Attacker with admin credentials can upload arbitrary files including web shells to the server without restrictions. |
| Impact | While CVSS and EPSS scores are unavailable, the real-world risk is extremely high based on the vulnerability mechanics and intelligence signals. The attack vector is network-based with no authentication required (typical for WordPress plugin upload handlers), and the technical impact is critical—successful exploitation grants remote code execution capability through web shell deployment. The absence of CVSS/EPSS data suggests either recent discovery or incomplete disclosure, but the CWE-434 classification combined with web shell upload capability indicates this is actively exploitable without complex prerequisites. The Patchstack reporting and ENISA EUVD registration (EUVD-2026-15888) confirm formal vulnerability tracking. This should be treated as a priority patch regardless of missing CVSS metrics, as file upload-to-RCE chains are frequently automated in real-world attacks. |
| Exploit ScenarioDerived | An unauthenticated attacker navigates to the vulnerable Photo Engine upload endpoint and submits a PHP web shell disguised with a benign filename or by exploiting insufficient MIME-type checking. The plugin accepts the file without proper validation and stores it in a web-accessible directory such as wp-content/uploads/. The attacker then accesses the uploaded shell via HTTP (e.g., https://target.com/wp-content/uploads/shell.php), gaining arbitrary code execution on the server with the privileges of the web server process. From this foothold, the attacker can escalate to database compromise, lateral movement, or deployment of persistent backdoors. No special authentication, user interaction, or complex exploitation techniques are required—this is a direct, high-probability attack path suitable for automated scanning and exploitation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 25, 2026
An unrestricted file upload vulnerability (CWE-434) exists in Jordy Meow's Photo Engine WordPress plugin versions up to and including 6.4.9, allowing attackers to upload malicious web shells to compromised servers. The vulnerability affects the wplr-sync component and permits arbitrary file uploads with dangerous types, potentially leading to remote code execution. No CVSS score, EPSS probability, or KEV status information is currently available, but the ability to upload executable web shells represents a critical exploitation path.
RemediationAI
Immediately upgrade Jordy Meow Photo Engine to a version newer than 6.4.9; contact the vendor (Patchstack maintains this plugin data) for the latest patched release. Until a patch is available, disable the wplr-sync upload functionality entirely via plugin configuration or remove the plugin if not essential. Implement file upload restrictions at the web server level using Apache/Nginx rules to block execution of scripts in upload directories (e.g., adding .htaccess or nginx location blocks to deny PHP execution in wp-content/uploads). Additionally, apply strict file type validation at the web application firewall or reverse proxy, restrict plugin upload capabilities to authenticated users only if available, and monitor upload directories for suspicious file creations using SIEM or file integrity monitoring tools. For comprehensive protection, review other custom WordPress plugins for similar CWE-434 issues.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in the Photo Engine WordPress plugin (CPE: cpe:2.3:a:jordy_meow:photo_engine:*:*:*:*:*:*:*:*) specifically within the wplr-sync upload handler component. The root cause is classified as CWE-434 (Unrestricted Upload of File with Dangerous Type), a fundamental file upload validation failure where the application fails to properly validate, sanitize, or restrict the type of files users can upload. The plugin accepts file uploads without adequate checks on file extension, MIME type, or content inspection, allowing attackers to bypass intended restrictions and place executable files (PHP shells, etc.) into web-accessible directories. This is a common vulnerability class in WordPress plugins where custom upload handlers are implemented without proper security controls.
Know when Photo Engine gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
Unrestricted Upload of File with Dangerous Type vulnerability in Jordy Meow Photo Engine wplr-sync allows Upload a Web Shell to a Web Server.This issue affects Photo Engine: from n/a through <= 6.4.9.
Executive ViewAI
CVE-2026-32524 presents critical security risk, a unrestricted file upload vulnerability rated CVSS 9.1. This could allow attackers to access or modify files outside intended directories, potentially exposing sensitive configuration or credentials. Organizations should apply vendor updates immediately when available and implement compensating controls in the interim.
Apply vendor patch. If immediate patching is not feasible: (1) Restrict file upload functionality via WAF; (2) Implement allowlist-based file type validation; (3) Use chroot/containerization to limit filesystem access.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
More in Photo Engine
View allMissing Authorization vulnerability in Jordy Meow Photo Engine allows Exploiting Incorrectly Configured Access Control S
Authorization Bypass Through User-Controlled Key vulnerability in Jordy Meow Photo Engine (Media Organizer & Lightroom).
EUVD-2026-15888
GHSA-v47h-99v4-c43h
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB