CVE-2024-1158

Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC) <= 2.8.7 - Missing Authorization

2024-03-06 00:00
Lucio Sá

Strategic Overview

Status
Patched in 2.8.8
Affected Plugin
Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC)
Affected Version
<= 2.8.7
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-1158
View all Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC) vulnerabilities

At a glance

CVE-2024-1158 is a medium-severity Missing Authorization vulnerability in the Post Form WordPress plugin, affecting versions <= 2.8.7. 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 2.8.8; sites on affected versions should update now. Disclosed March 2024, reported by Lucio Sá.

Vulnerability Overview

The Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the buddyforms_new_page function in all versions up to, and including, 2.8.7. This makes it possible for authenticated attackers, with subscriber access or higher, to create pages with arbitrary titles. These pages are published.

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 Post Form <= 2.8.7 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 Post Form the fix is 2.8.8: builds <= 2.8.7 are affected, anything from 2.8.8 onward is not.

Remediation

Update to version 2.8.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: Post Form 2.8.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-1158https://www.wordfence.com/threat-intel/vulnerabilities/id/198cb3bb-73fe-45ae-b8e0-b7ee8dda9547https://nvd.nist.gov/vuln/detail/CVE-2024-1158

Related records

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