The User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.3.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to delete arbitrary media attachments whose post_author is 0, such as guest and registration-form uploads, via the wpuf_file_del AJAX action. This is exploitable by unauthenticated visitors on any site where a WPUF shortcode is rendered on a front-end page, as this causes the valid wpuf_nonce value to be localized into publicly accessible JavaScript objects (wpuf_upload and wpuf_frontend), satisfying the sole access control gate.
CVE-2026-12406
Score 5.3 from GitHub Security Advisory published 2026-07-09. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 24(Track)EG Risk 24/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
July 9, 2026
Last Modified
July 9, 2026
References (10)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.2/includes/Ajax.php#L27
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.2/includes/Ajax/Upload_Ajax.php#L257
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.2/includes/Ajax/Upload_Ajax.php#L271
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.2/includes/Frontend.php#L88
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.7/includes/Ajax.php#L27
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.7/includes/Ajax/Upload_Ajax.php#L257
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.7/includes/Ajax/Upload_Ajax.php#L271
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.7/includes/Frontend.php#L88
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?reponame=&old=3578622%40wp-user-frontend&new=3578622%40wp-user-frontend
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/0049583a-0ad3-45e4-a29e-4b8c33d09857?source=cve
Vendor Advisories for CVE-2026-12406(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 45× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-31 03:13 UTCEG score recompute
- 2026-07-31 03:12 UTCGHSA enrichment
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 05:03 UTCEG score recompute
- 2026-07-30 05:03 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 06:54 UTCEG score recompute
- 2026-07-29 06:54 UTCGHSA enrichment
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-28 08:42 UTCEG score recompute
- 2026-07-28 08:42 UTCGHSA enrichment
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 10:33 UTCEG score recompute
- 2026-07-27 10:32 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 12:22 UTCEG score recompute
- 2026-07-26 12:22 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
Show 20 moreShow fewer
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:26 UTCGHSA enrichment
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-15 19:16 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 21:05 UTCGHSA enrichment
- 2026-07-13 22:56 UTCGHSA enrichment
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-13 00:46 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 02:34 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 04:25 UTCGHSA enrichment
- 2026-07-10 06:15 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 08:02 UTCEG score recompute
- 2026-07-09 08:01 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-12406?
When was CVE-2026-12406 disclosed?
Is CVE-2026-12406 actively exploited?
What is the CVSS score of CVE-2026-12406?
How do I remediate CVE-2026-12406?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-12406
Is Your Infrastructure Affected by CVE-2026-12406?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.