dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-12418

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 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.

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 WPUF WordPress plugin has an IDOR vulnerability in the 'wpuf_files_data' parameter that lacks validation on user-controlled keys. Unauthenticated attackers can overwrite post_title, post_content, and post_excerpt of any post on the site, including administrator-authored posts, by submitting requests through any WPUF post submission form. The wpuf_submit_post AJAX action is protected only by a nonce but lacks capability checks for the downstream post-edit operation.

MitigationUpdate to WPUF version 4.3.8 or later which adds proper capability checks and validates user permissions before allowing post modifications.

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. Confirm WPUF plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WordPress User Frontend' or check the file /wp-content/plugins/wpuf/ exists on the server
    Affected if WPUF plugin is active on the site
  2. Check installed WPUF version
    View the plugin file header at /wp-content/plugins/wpuf/readme.txt or /wp-content/plugins/wpuf/wpuf.php to find the Version: field, then compare to 4.3.8
    Affected if Installed version is lower than 4.3.8
  3. Verify wpuf_submit_post AJAX is accessible
    Check if the AJAX action /wp-admin/admin-ajax.php?action=wpuf_submit_post responds to requests; test with a crafted request containing wpuf_files_data parameter
    Affected if AJAX endpoint responds without requiring capability validation
  4. Inspect WPUF form submissions for post ID targeting
    Review the WPUF form settings in admin panel at User Frontend > Post Forms to see if forms allow submission to existing posts (edit mode) without ownership verification
    Affected if Forms permit targeting arbitrary post IDs for modification

The site is affected if WPUF plugin version is below 4.3.8 and the wpuf_submit_post AJAX action is accessible without proper capability checks on the post ID being modified.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to WPUF version 4.3.8 or later which adds proper capability checks and validates user permissions before allowing post modifications.

Recommended fix Moderate confidence

User Frontend plugin version 4.3.8 or later

  1. Check if a newer version of the User Frontend (WPUF) plugin is available in the WordPress plugin repository
  2. If version 4.3.8 or later is available, upgrade to that version
  3. Verify the upgrade resolves the issue by ensuring proper capability checks are in place for the wpuf_submit_post AJAX action
  4. Confirm that wpuf_files_data parameter validation prevents unauthorized post modifications

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12418 — 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-12418 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