Pie Register <= 3.8.3.2 - Unauthenticated Arbitrary File Upload
Strategic Overview
- Status
- Patched in 3.8.3.3
- Affected Version
<= 3.8.3.2- CVSS
- 9.8Critical
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2024-27957
At a glance
CVE-2024-27957 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Pie Register WordPress plugin, affecting versions <= 3.8.3.2. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.8.3.3; sites on affected versions should update now. Disclosed March 2024, reported by Rafie Muhammad.
Vulnerability Overview
The Pie Register plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the pie_save_registration function in versions up to, and including, 3.8.3.2. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. NOTE: This vulnerability presents itself when the 'Anyone can register' option is enabled in options-general and the 'Upload File' field is added to the registration form.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
Reaching this weakness in Pie Register <= 3.8.3.2 takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Pie Register the fix is 3.8.3.3: builds <= 3.8.3.2 are affected, anything from 3.8.3.3 onward is not.
Remediation
Update to version 3.8.3.3, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Pie Register 3.8.3.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Other vulnerabilities in Pie Register – User Registration, Profiles & Content Restriction
- 9.8CVE-2025-34077: Pie Register <= 3.7.1.4 Authentication Bypass
CVE-2025-34077 - 9.8CVE-2021-24731: Pie Register <= 3.7.1.5 SQL Injection
CVE-2021-24731 - 9.8CVE-2019-15659: Pie Register SQL Injection
CVE-2019-15659 - 9.8CVE-2018-10969: Pie Register <= 3.0.9 SQL Injection
CVE-2018-10969 - 9.8Registration Forms Authentication Bypass
- 9.8Pie Register 2.0.14-2.0.15 SQL Injection
- 8.8CVE-2024-6069: Pie Register - Basic Authenticated (Subscriber+)
CVE-2024-6069 - 8.1CVE-2021-24647: Pie Register <= 3.7.1.5 Authentication Bypass
CVE-2021-24647
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C