CVE-2024-47377

BuddyForms <= 2.8.12 - Authenticated (Editor+) Stored Cross-Site Scripting

2024-09-30 00:00
SOPROBRO

Strategic Overview

Status
Patched in 2.8.13
Affected Plugin
Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC)
Affected Version
<= 2.8.12
CVSS
4.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2024-47377
View all Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC) vulnerabilities

At a glance

CVE-2024-47377 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Post Form WordPress plugin, affecting versions <= 2.8.12. It carries a CVSS score of 4.4 (reachable over the network). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 2.8.13; sites on affected versions should update now. Disclosed September 2024, reported by SOPROBRO.

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 Stored Cross-Site Scripting via settings in all versions up to, and including, 2.8.12 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in Post Form <= 2.8.12 takes an account at Editor level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Post Form the fix is 2.8.13: builds <= 2.8.12 are affected, anything from 2.8.13 onward is not.

Remediation

Update to version 2.8.13, or a newer patched version

How does WordSec protect against this?

An attacker needs Editor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Post Form 2.8.13 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-47377https://www.wordfence.com/threat-intel/vulnerabilities/id/ac8a06f5-4560-401c-b762-5422b624ba84https://nvd.nist.gov/vuln/detail/CVE-2024-47377

Related records

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