Unauthenticated code execution via upload loop mismatch
Published Aug 19, 2026 · Updated Aug 20, 2026
Arbitrary file upload in Elementor Elementor Pro before 4.2.2 allows remote attackers to execute PHP via the Form widget upload field. In modules/forms/fields/upload.php, validation() returns on an initial UPLOAD_ERR_NO_FILE entry while process_field() only continues past it, so a second part for the same field bypasses is_file_type_valid() and is moved with its .php extension intact into wp-content/uploads/elementor/forms/. Exposure requires a published Form widget with a non-required File Upload field, after which an unauthenticated visitor can request the uploaded PHP file directly for server-side code execution.
Summary
What happened
Arbitrary file upload in Elementor Elementor Pro before 4.2.2 allows remote attackers to execute PHP via the Form widget upload field. In modules/forms/fields/upload.php, validation() returns on an initial UPLOAD_ERR_NO_FILE entry while process_field() only continues past it, so a second part for the same field bypasses is_file_type_valid() and is moved with its .php extension intact into wp-content/uploads/elementor/forms/. Exposure requires a published Form widget with a non-required File Upload field, after which an unauthenticated visitor can request the uploaded PHP file directly for server-side code execution.
The record
- CVE
- CVE-2026-32475
- Published
- Aug 19, 2026
- Updated
- Aug 20, 2026
- Vendor
- Elementor
- Product
- Elementor Pro
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=4.2.1 changes=[{"at":"4.2.2","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo