CVE-2022-4239

Workreap <= 2.6.3 - Insecure Direct Object Reference

2022-12-02 00:00
Veshraj Ghimire

Strategic Overview

Status
Patched in 2.6.4
Affected Version
<= 2.6.3
CVSS
5.4Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2022-4239
View all Workreap - Freelance Marketplace and Directory WordPress Theme vulnerabilities

At a glance

CVE-2022-4239 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Workreap - Freelance Marketplace and Directory WordPress Theme WordPress theme, affecting versions <= 2.6.3. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The issue is fixed in version 2.6.4; sites on affected versions should update now. Disclosed December 2022, reported by Veshraj Ghimire.

Vulnerability Overview

The Workreap theme for WordPress is vulnerable to insecure direct object reference in versions up to, and including, 2.6.3. This is due to missing validation on if an addon service belongs to an individual making a request to the workreap_addons_service_remove action. This makes it possible for authenticated attackers to call arbitrary addon services and delete posts.

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

Reaching this weakness in Workreap - Freelance Marketplace and Directory WordPress Theme <= 2.6.3 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 Workreap - Freelance Marketplace and Directory WordPress Theme the fix is 2.6.4: builds <= 2.6.3 are affected, anything from 2.6.4 onward is not.

Remediation

Update to version 2.6.4, 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: Workreap - Freelance Marketplace and Directory WordPress Theme 2.6.4 closes this, and updating the theme is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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