Comments Extra Fields For Post,Pages and CPT <= 5.0 - Missing Authorization
Strategic Overview
- Status
- Patched in 5.1
- Affected Plugin
- Comments Extra Fields For Post,Pages and CPT
- Affected Version
<= 5.0- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-0829
At a glance
CVE-2024-0829 is a medium-severity Missing Authorization vulnerability in the Comments Extra Fields For Post,Pages and CPT WordPress plugin, affecting versions <= 5.0. 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.1; sites on affected versions should update now. Disclosed February 2024, reported by Francesco Carlucci.
Vulnerability Overview
The Comments Extra Fields For Post,Pages and CPT plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 5.0. This is due to missing or incorrect capability checks on several ajax actions. This makes it possible for authenticated attackers, with subscriber access or higher, to invoke those actions. As a result, they may modify comment form fields and update plugin settings.
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
Reaching this weakness in Comments Extra Fields For Post,Pages and CPT <= 5.0 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 Comments Extra Fields For Post,Pages and CPT the fix is 5.1: builds <= 5.0 are affected, anything from 5.1 onward is not.
Remediation
Update to version 5.1, 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: Comments Extra Fields For Post,Pages and CPT 5.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Comments Extra Fields For Post,Pages and CPT
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C