BuddyForms <= 2.8.8 - Unauthenticated Arbitrary File Read and Server-Side Request Forgery
Strategic Overview
- Status
- Patched in 2.8.9
- Affected Plugin
- Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC)
- Affected Version
<= 2.8.8- CVSS
- 9.3Critical
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2024-32830
At a glance
CVE-2024-32830 is a critical-severity Server-Side Request Forgery (SSRF) vulnerability in the Post Form WordPress plugin, affecting versions <= 2.8.8. It carries a CVSS score of 9.3 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.8.9; sites on affected versions should update now. Disclosed April 2024, reported by beluga.
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 Arbitrary File Read and Server-Side Request Forgery in all versions up to, and including, 2.8.8. This makes it possible for unauthenticated attackers to read arbitrary files on the server and make requests to internal services.
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 confidentiality.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in Post Form <= 2.8.8 takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Post Form the fix is 2.8.9: builds <= 2.8.8 are affected, anything from 2.8.9 onward is not.
Remediation
Update to version 2.8.9, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Post Form 2.8.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC)
- 9.8CVE-2018-21003: Post, Registration and Profile Form… SQL Injection
CVE-2018-21003 - 8.8CVE-2025-32151: BuddyForms <= 2.8.17 Local File Inclusion
CVE-2025-32151 - 8.8CVE-2024-8246: Post Form Privilege Escalation
CVE-2024-8246 - 8.8CVE-2023-26326: BuddyForms <= 2.7.7 PHAR Deserialization
CVE-2023-26326 - 8.8Freemius SDK <= 2.2.3 Arbitrary Options Update
- 8.2CVE-2024-1170: Post Form Unauthenticated Media Deletion
CVE-2024-1170 - 7.5CVE-2024-1169: Post Form Unauthenticated Media Upload
CVE-2024-1169 - 6.5CVE-2024-5149: BuddyForms Email Verification Bypass
CVE-2024-5149
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C