CVE-2024-43235

Meta Box – WordPress Custom Fields Framework <= 5.9.10 - Missing Authorization to Information Exposure

2024-08-09 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 5.9.11
Affected Plugin
Meta Box – A Framework for Dynamic Websites
Affected Version
<= 5.9.10
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-43235
View all Meta Box – A Framework for Dynamic Websites vulnerabilities

At a glance

CVE-2024-43235 is a medium-severity Missing Authorization vulnerability in the Meta Box WordPress plugin, affecting versions <= 5.9.10. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 5.9.11; sites on affected versions should update now. Disclosed August 2024, reported by Rafie Muhammad.

Vulnerability Overview

The Meta Box – WordPress Custom Fields Framework plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the query function called via 'ajax_get_posts' in versions up to, and including, 5.9.10. This makes it possible for authenticated attackers, with contributor-level access and above, to view arbitrary 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-862: Missing Authorization

Meta Box <= 5.9.10 carries this weakness at ajax_get_posts, and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Meta Box the fix is 5.9.11: builds <= 5.9.10 are affected, anything from 5.9.11 onward is not.

Remediation

Update to version 5.9.11, 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: Meta Box 5.9.11 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-43235https://www.wordfence.com/threat-intel/vulnerabilities/id/9a49b72f-9ad9-4338-aeeb-d81be58e1c15https://nvd.nist.gov/vuln/detail/CVE-2024-43235

Related records

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