Career Section <= 1.7 - Unauthenticated Arbitrary File Upload
Strategic Overview
- Status
- Patched in 1.8
- Affected Plugin
- Career Section
- Affected Version
<= 1.7- CVSS
- 9.8Critical
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2026-6271
At a glance
CVE-2026-6271 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Career Section WordPress plugin, affecting versions <= 1.7. 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 1.8; sites on affected versions should update now. Disclosed May 2026, reported by Paolo Tresso.
Vulnerability Overview
The Career Section plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 1.7 via the CV upload handler. This is due to missing file type validation. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes 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 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 Career Section <= 1.7 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 Career Section the fix is 1.8: builds <= 1.7 are affected, anything from 1.8 onward is not.
Remediation
Update to version 1.8, 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: Career Section 1.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Other vulnerabilities in Career Section
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C