CVE-2024-3748

SP Project & Document Manager <= 4.71 - Insecure Direct Object Reference

2024-04-24 00:00
fewwords huang

Strategic Overview

Status
Unpatched
Affected Version
<= 4.71
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-3748
View all SP Project & Document Manager vulnerabilities

At a glance

CVE-2024-3748 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the SP Project & Document Manager WordPress plugin, affecting versions <= 4.71. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). No fixed release has been reported yet; treat installations running this software as exposed. Disclosed April 2024, reported by fewwords huang.

Vulnerability Overview

The SP Project & Document Manager plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.71 via the sp_cdm_link_save_embed AJAX action to missing validation on the 'user_id' user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload files that look like they were uploaded by another user.

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

SP Project & Document Manager <= 4.71 carries this weakness at user_id, 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. No fixed build of this plugin is recorded for SP Project & Document Manager yet, so installs running <= 4.71 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

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