CVE-2026-12418 json
User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration <= 4.3.7 - Insecure Direct Object Reference to Unauthenticated Arbitrary Post Modification via 'wpuf_files_data' Parameter
published 2026-07-09 4 mo ago modified 2026-07-09 4 mo ago also EUVD-2026-42542
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
The User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.3.7 via the 'wpuf_files_data' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to overwrite the post_title, post_content, and post_excerpt of any arbitrary post on the site, including posts authored by administrators. Exploitation requires access to any WPUF post submission form; this is achievable by users with no WordPress role, as the wpuf_submit_post AJAX action is gated only by a nonce with no capability check for the downstream post-edit operation.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- wedevs User Frontend: AI Powered Frontend Posting, User Directory, Profile Builder, Membership & User Registration
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/8f66e25f-b67e-4227-95fe-69b40551af61?source=cve
- plugins.trac.wordpress.org /browser/wp-user-frontend/tags/4.3.6/includes/Traits/FieldableTrait.php#L478
- plugins.trac.wordpress.org /browser/wp-user-frontend/tags/4.3.6/includes/Ajax/Frontend_Form_Ajax.php#L35
- plugins.trac.wordpress.org /browser/wp-user-frontend/tags/4.3.6/includes/Traits/FieldableTrait.php#L468
- plugins.trac.wordpress.org /browser/wp-user-frontend/tags/4.3.1/includes/Traits/FieldableTrait.php#L478
- plugins.trac.wordpress.org /browser/wp-user-frontend/tags/4.3.1/includes/Ajax/Frontend_Form_Ajax.php#L35
- plugins.trac.wordpress.org /browser/wp-user-frontend/tags/4.3.1/includes/Traits/FieldableTrait.php#L468
- plugins.trac.wordpress.org /changeset?reponame=&old=3578622%40wp-user-frontend&new=3578622%40wp-user-frontend
Sources
- CVE List CVE-2026-12418
- NVD CVE-2026-12418
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.