Subscriber-level PHP upload via missing type validation
Published Dec 12, 2022 · Updated Apr 22, 2025
Arbitrary file upload in WPEverest User Registration before 2.2.4.1 allows remote authenticated users to place executable PHP files. The profile_pic_upload AJAX function accepts attacker-controlled uploads without enforcing an allowed file type before storing them on the WordPress server. Subscriber-level access is sufficient, and a PHP payload placed in a web-accessible upload location enables server-side code execution.
Summary
What happened
Arbitrary file upload in WPEverest User Registration before 2.2.4.1 allows remote authenticated users to place executable PHP files. The profile_pic_upload AJAX function accepts attacker-controlled uploads without enforcing an allowed file type before storing them on the WordPress server. Subscriber-level access is sufficient, and a PHP payload placed in a web-accessible upload location enables server-side code execution.
The record
- CVE
- CVE-2022-3912
- Published
- Dec 12, 2022
- Updated
- Apr 22, 2025
- Vendor
- WPEverest
- Product
- User Registration & Membership
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 12, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record 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=0 <2.2.4.1
What conditions does exploitation require?
What is affected?
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
- WPScan exploit entry for subscriber-level arbitrary file uploadproof of concept · unverified
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