Workreap <= 3.3.2 - Authenticated (Subscriber+) Arbitrary File Upload via 'workreap_temp_upload_to_media'
Strategic Overview
- Status
- Patched in 3.3.3
- Affected Plugin
- Workreap
- Affected Version
<= 3.3.2- CVSS
- 8.8High
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2025-5012
At a glance
CVE-2025-5012 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Workreap WordPress plugin, affecting versions <= 3.3.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.3.3; sites on affected versions should update now. Disclosed June 2025, reported by Foxyyy.
Vulnerability Overview
The Workreap plugin for WordPress, used by the Workreap - Freelance Marketplace WordPress Theme, is vulnerable to arbitrary file uploads due to missing file type validation in the 'workreap_temp_upload_to_media' function in all versions up to, and including, 3.3.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 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
Workreap <= 3.3.2 carries this weakness at workreap_temp_upload_to_media, and reaching it takes an account at Subscriber level or above. 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 Workreap the fix is 3.3.3: builds <= 3.3.2 are affected, anything from 3.3.3 onward is not.
Remediation
Update to version 3.3.3, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: 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: Workreap 3.3.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Workreap
- 9.8CVE-2025-4973: Workreap <= 3.3.1 Authentication Bypass
CVE-2025-4973 - 9.8CVE-2024-13446: Workreap <= 3.2.5 Privilege Escalation
CVE-2024-13446 - 8.1CVE-2025-59566: Workreap <= 3.3.5 Arbitrary File Deletion
CVE-2025-59566 - 8.1CVE-2021-24500: Workreap < 2.2.2 Cross-Site Request Forgery
CVE-2021-24500 - 8.1CVE-2021-24501: Workreap Theme < 2.2.2 Authorization Bypass
CVE-2021-24501 - 6.5CVE-2025-22728: Workreap (theme's plugin) <= 3.3.6 SQL Injection
CVE-2025-22728 - 5.4CVE-2022-4239: Workreap <= 2.6.3 Insecure Direct Object Reference
CVE-2022-4239 - 5.4CVE-2022-3846: Workreap Insecure Direct Objection Reference
CVE-2022-3846
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C