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

CVE-2026-5459

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-08
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.1 via the payment_page() function due to missing validation on the 'user_id' user controlled key. This makes it possible for unauthenticated attackers to activate a free subscription pack for any user on the site, overwriting their existing paid subscription and causing loss of paid features.

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 WordPress plugin 'User Frontend' has an IDOR vulnerability in the payment_page() function that lacks validation on the user_id parameter. This allows unauthenticated attackers to submit requests specifying any user ID and activate a free subscription pack for that user, overwriting their existing paid subscription and causing loss of paid features.

MitigationUpdate to a patched version of the plugin when available. Until then, restrict access to the payment_page() function or implement proper authorization checks validating that the current user owns the specified user_id before processing subscription changes.

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 User Frontend plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'User Frontend' or check the file wp-content/plugins/user-frontend/ for existence. Check plugin version in plugin header or readme.txt
    Affected if Plugin is installed and active
  2. Verify payment functionality is exposed
    Look for the payment_page shortcode or endpoint. Common paths include shortcode usage in pages (e.g., [user_frontend_payment]) or direct URL access to payment-related routes. Check if any page uses the payment shortcode or if the payment_page function is callable via web request
    Affected if The payment_page function or payment shortcode is publicly accessible
  3. Confirm subscription feature is enabled
    Check WordPress plugin settings for User Frontend. Look for subscription/payment configuration options in the plugin admin panel. Verify that any subscription pack or payment feature has been created and is active
    Affected if Subscription or payment features are configured and active in the plugin settings
  4. Check for missing user_id authorization
    Inspect the payment_page() function code in the plugin file (typically user-frontend/wpuf-functions.php or similar). Look for code that handles the user_id parameter without verifying the current user owns that ID. Search for code like $_GET['user_id'] or $_POST['user_id'] being used directly without current_user_can() or ownership validation
    Affected if The user_id parameter is processed without proper authorization checks validating user ownership

If the User Frontend plugin is installed with subscription/payment features enabled and the payment_page function is publicly accessible without user ownership validation, the environment is affected by this IDOR vulnerability.

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 a patched version of the plugin when available. Until then, restrict access to the payment_page() function or implement proper authorization checks validating that the current user owns the specified user_id before processing subscription changes.

Recommended fix Moderate confidence

Latest version available in the WordPress plugin repository (newer than 4.3.1)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration'
  4. If an update is available, click 'Update Now'
  5. After updating, verify the payment_page() function has proper user_id validation by checking plugin changelog or release notes
  6. Consider reviewing user subscription status in the membership/payments settings to ensure no unauthorized changes occurred
Caveat Review plugin changelog for any breaking changes between current installed version and new version before updating on production sites

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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