Job Manager <= 0.7.25 - Insecure Direct Object Reference
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Job Manager
- Affected Version
<= 0.7.25- CVSS
- 7.5High
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2015-6668
At a glance
CVE-2015-6668 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the Job Manager WordPress plugin, affecting versions <= 0.7.25. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2015, reported by Evangelos Mourikis.
Vulnerability Overview
The Job Manager plugin before 0.7.25 allows remote attackers to read arbitrary CV files via a brute force attack to the WordPress upload directory structure, related to an insecure direct object reference.
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.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Job Manager <= 0.7.25 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. No fixed build of this plugin is recorded for Job Manager yet, so installs running <= 0.7.25 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Job Manager
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C