dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-12406

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The User Frontend WordPress plugin versions up to 4.3.7 contains an authorization bypass vulnerability in the wpuf_file_del AJAX action. Unauthenticated attackers can delete arbitrary media attachments where post_author is 0 (guest uploads) because the wpuf_nonce is exposed in publicly accessible JavaScript objects (wpuf_upload and wpuf_frontend), allowing attackers to satisfy the sole access control check.

MitigationUpdate to the latest patched version of the plugin when available. Until patched, consider disabling WPUF shortcodes on public-facing pages or implementing web application firewall rules to block unauthorized wpuf_file_del requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > User Frontend (or check wp-content/plugins/wpuf/version.php). Compare the version number to the affected range (up to 4.3.7).
    Affected if The installed version is 4.3.7 or lower.
  2. Identify guest-uploaded media
    Query your WordPress database: SELECT ID, post_title, post_date FROM wp_posts WHERE post_type = 'attachment' AND post_author = 0; (adjust wp_ prefix if different).
    Affected if There are media attachments with post_author = 0 (guest uploads) in the database.
  3. Verify AJAX endpoint accessibility
    Check if the wpuf_file_del AJAX action is exposed to unauthenticated users by inspecting the plugin code in wp-content/plugins/wpuf/includes/class-ajax.php or testing: curl -X POST https://yoursite.com/wp-admin/admin-ajax.php -d 'action=wpuf_file_del' -d 'post_id=1'
    Affected if The AJAX action responds without requiring authentication (returns nonce error rather than auth error).
  4. Confirm nonce exposure in frontend
    View page source of a public page with WPUF shortcodes. Search for 'wpuf_upload' or 'wpuf_frontend' JavaScript objects for a 'nonce' or 'wpuf_nonce' property.
    Affected if The nonce value is visible in publicly accessible JavaScript variables on the frontend.

You are affected if the plugin version is 4.3.7 or lower, the site has guest-uploaded media (post_author=0), and the AJAX endpoint is accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of the plugin when available. Until patched, consider disabling WPUF shortcodes on public-facing pages or implementing web application firewall rules to block unauthorized wpuf_file_del requests.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12406 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12406 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data