CVE-2024-1170

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

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
8.2High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-1170
View all Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC) vulnerabilities

At a glance

CVE-2024-1170 is a high-severity Missing Authorization vulnerability in the Post Form WordPress plugin, affecting versions <= 2.8.7. It carries a CVSS score of 8.2 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. 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 media file deletion due to a missing capability check on the handle_deleted_media function in all versions up to, and including, 2.8.7. This makes it possible for unauthenticated attackers to delete arbitrary media files.

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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity.

CWE-862: Missing Authorization

Reaching this weakness in Post Form <= 2.8.7 takes no account at all. 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?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. 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-1170https://www.wordfence.com/threat-intel/vulnerabilities/id/380c646c-fd95-408a-89eb-3e646768bbc5https://nvd.nist.gov/vuln/detail/CVE-2024-1170

Related records

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