CVE-2023-7049

Custom Field For WP Job Manager <= 1.2 - Insecure Direct Object Reference to Sensitive Information Exposure via Shortcode

2024-08-15 00:00
Francesco Carlucci

Strategic Overview

Status
Patched in 1.3
Affected Plugin
Custom Field For WP Job Manager
Affected Version
<= 1.2
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-7049
View all Custom Field For WP Job Manager vulnerabilities

At a glance

CVE-2023-7049 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Custom Field For WP Job Manager WordPress plugin, affecting versions <= 1.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 1.3; sites on affected versions should update now. Disclosed August 2024, reported by Francesco Carlucci.

Vulnerability Overview

The Custom Field For WP Job Manager plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.2 via the the 'cm_fieldshow' shortcode due to missing validation on the 'job_id' user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to expose potentially sensitive post metadata.

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.

CWE-639: Authorization Bypass Through User-Controlled Key

Custom Field For WP Job Manager <= 1.2 carries this weakness at cm_fieldshow, and reaching it 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. For Custom Field For WP Job Manager the fix is 1.3: builds <= 1.2 are affected, anything from 1.3 onward is not.

Remediation

Update to version 1.3, or a newer patched version

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. None of that substitutes for the fix: Custom Field For WP Job Manager 1.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-7049https://www.wordfence.com/threat-intel/vulnerabilities/id/9891587b-2a63-41be-b79d-afe407dd57fahttps://nvd.nist.gov/vuln/detail/CVE-2023-7049

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C