CVE-2024-30507

Molongui <= 4.7.7 - Authenticated (Author+) Insecure Direct Object Reference

2024-03-28 00:00
CatFather

Strategic Overview

Status
Patched in 4.7.8
Affected Plugin
Molongui Authorship – Author Boxes, Guest Authors & Co-Authors for WordPress
Affected Version
<= 4.7.7
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-30507
View all Molongui Authorship – Author Boxes, Guest Authors & Co-Authors for WordPress vulnerabilities

At a glance

CVE-2024-30507 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Molongui Authorship WordPress plugin, affecting versions <= 4.7.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 4.7.8; sites on affected versions should update now. Disclosed March 2024, reported by CatFather.

Vulnerability Overview

The Author Box, Guest Author and Co-Authors for Your Posts – Molongui plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.7.7 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with author-level access and above, to perform an unauthorized action.

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 Molongui Authorship <= 4.7.7 takes an account at Author level or above. 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 Molongui Authorship the fix is 4.7.8: builds <= 4.7.7 are affected, anything from 4.7.8 onward is not.

Remediation

Update to version 4.7.8, 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: Molongui Authorship 4.7.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-30507https://www.wordfence.com/threat-intel/vulnerabilities/id/62aa0cc4-ef8e-4727-ac07-3481c0464b05https://nvd.nist.gov/vuln/detail/CVE-2024-30507

Related records

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