dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-10299

HIGH · 8.8 CVSS v3.1 Published 2025-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 WPBifröst – Instant Passwordless Temporary Login Links plugin for WordPress is vulnerable to Privilege Escalation due to a missing capability check on the ctl_create_link AJAX action in all versions up to, and including, 1.0.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create new administrative user accounts and subsequently log in as those.

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 WPBifröst plugin for WordPress has a privilege escalation vulnerability in its AJAX handler. The ctl_create_link AJAX action lacks capability validation, allowing any authenticated user with Subscriber-level access to create new administrative user accounts and gain full system access.

MitigationUpdate the plugin to version 1.0.8 or later which includes proper capability checks on the AJAX action. Until then, consider disabling the plugin or restricting user registration.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify WPBifröst plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for WPBifröst in the list, or check the /wp-content/plugins/ directory for a folder named 'wpbifrost' or similar.
    Affected if The plugin appears in the installed plugins list and is activated.
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate the WPBifröst plugin entry. The version number is displayed below the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/[plugin-folder]/wpbifrost.php for the Version field.
    Affected if The installed version is lower than 1.0.8 (e.g., 1.0.7, 1.0.6, or any version prior to 1.0.8).
  3. Confirm the AJAX action is accessible to low-privilege users
    Test whether the ctl_create_link AJAX action is reachable. This typically involves sending a request to /wp-admin/admin-ajax.php with action=ctl_create_link while logged in as a Subscriber-level user. Check the plugin source code for the registered AJAX handler for 'ctl_create_link' and verify if add_action('wp_ajax_ctl_create_link', ...) lacks a current_user_can() or capability check before processing.
    Affected if The AJAX endpoint responds to requests from authenticated users with Subscriber role and the code does not perform a capability check before executing the create link logic.
  4. Verify if administrative users can be created via the endpoint
    As a low-privileged user (Subscriber), attempt to submit a request to the ctl_create_link AJAX action with parameters that would create an administrative account (e.g., user_login, user_email, role=administrator). Observe if the request succeeds without authorization errors.
    Affected if The action successfully creates an administrative user account when invoked by a Subscriber-level user.

You are affected if the WPBifröst plugin is installed with a version lower than 1.0.8 and the ctl_create_link AJAX action can be accessed by Subscriber-level users without capability validation.

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 the plugin to version 1.0.8 or later which includes proper capability checks on the AJAX action. Until then, consider disabling the plugin or restricting user registration.

Recommended fix Moderate confidence

Version 1.0.8 or later of WPBifröst – Instant Passwordless Temporary Login Links plugin

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the 'WPBifröst – Instant Passwordless Temporary Login Links' plugin.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is running version 1.0.8 or later.
  7. 7. Review user accounts created recently to ensure no unauthorized administrative accounts were added.

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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