CVE-2024-1204

Meta Box – WordPress Custom Fields Framework <= 5.9.3 - Authenticated (Contributor+) Information Exposure via Post Meta

2024-03-25 00:00
Scott Kingsley Clark

Strategic Overview

Status
Patched in 5.9.4
Affected Version
<= 5.9.3
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-1204
View all Meta Box – A Framework for Dynamic Websites vulnerabilities

At a glance

CVE-2024-1204 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Meta Box WordPress plugin, affecting versions <= 5.9.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 5.9.4; sites on affected versions should update now. Disclosed March 2024, reported by Scott Kingsley Clark.

Vulnerability Overview

The Meta Box – WordPress Custom Fields Framework plugin for WordPress is vulnerable to information exposure in all versions up to, and including, 5.9.3. This is due to the plugin not properly restricting the post meta that can be displayed through the 'rwmb_meta' shortcode. This makes it possible for authenticated attackers, with contributor-level access and above, to retrieve arbitrary post meta information.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Meta Box <= 5.9.3 carries this weakness at rwmb_meta, and reaching it takes an account at Contributor level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Meta Box the fix is 5.9.4: builds <= 5.9.3 are affected, anything from 5.9.4 onward is not.

Remediation

Update to version 5.9.4, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Meta Box 5.9.4 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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