Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC) <= 2.8.11 - Authenticated (Contributor+) Privilege Escalation
Strategic Overview
- Status
- Patched in 2.8.12
- Affected Plugin
- Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC)
- Affected Version
<= 2.8.11- CVSS
- 8.8High
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2024-8246
At a glance
CVE-2024-8246 is a high-severity Improper Privilege Management vulnerability in the Post Form WordPress plugin, affecting versions <= 2.8.11. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.8.12; sites on affected versions should update now. Disclosed September 2024, reported by wesley (wcraft).
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 privilege escalation in all versions up to, and including, 2.8.11. This is due to plugin not properly restricting what users have access to set the default role on registration forms. This makes it possible for authenticated attackers, with contributor-level access and above, to create a registration form with a custom role that allows them to register as administrators.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-269: Improper Privilege Management
Reaching this weakness in Post Form <= 2.8.11 takes an account at Contributor level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For Post Form the fix is 2.8.12: builds <= 2.8.11 are affected, anything from 2.8.12 onward is not.
Remediation
Update to version 2.8.12, 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.12 closes this, and updating the plugin is the step that ends it.
- 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 - 9.3CVE-2024-32830: BuddyForms <= 2.8.8 Arbitrary File Read and SSRF
CVE-2024-32830 - 8.8CVE-2025-32151: BuddyForms <= 2.8.17 Local File Inclusion
CVE-2025-32151 - 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