dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-15027

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 JAY Login & Register plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.6.03. This is due to the plugin allowing a user to update arbitrary user meta through the 'jay_login_register_ajax_create_final_user' function. This makes it possible for unauthenticated attackers to elevate their privileges to that of an administrator.

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 JAY Login & Register WordPress plugin versions up to 2.6.03 contain a privilege escalation vulnerability in the 'jay_login_register_ajax_create_final_user' AJAX function. This function improperly allows unauthenticated users to update arbitrary user meta data, enabling attackers to modify their own user role to administrator.

MitigationUpdate the JAY Login & Register plugin to a version newer than 2.6.03, or if no patched version is available, remove the plugin entirely to prevent unauthenticated privilege escalation.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check if JAY Login & Register plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'jay-login-register' or similar naming pattern
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin > Plugins, locate JAY Login & Register and read the version number from the plugin description, or open the main plugin PHP file and locate the 'Version:' header comment
    Affected if Version is 2.6.03 or lower (including any 2.x.x version below 2.6.03)
  3. Confirm the vulnerable AJAX function exists
    Inspect the plugin files for the function named 'jay_login_register_ajax_create_final_user' or check if the AJAX action 'jay_login_register_ajax_create_final_user' is registered in WordPress
    Affected if The AJAX action is registered and accessible to unauthenticated users
  4. Verify AJAX endpoint allows unauthenticated user meta updates
    Test access to /wp-admin/admin-ajax.php?action=jay_login_register_ajax_create_final_user without authentication, or review plugin code to confirm the AJAX handler processes user meta updates without capability checks
    Affected if The endpoint accepts requests without authentication and allows modification of user role or meta data

A user is affected if the JAY Login & Register plugin version 2.6.03 or lower is installed and active, with the vulnerable AJAX function accessible to unauthenticated users.

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 JAY Login & Register plugin to a version newer than 2.6.03, or if no patched version is available, remove the plugin entirely to prevent unauthenticated privilege escalation.

Recommended fix Moderate confidence

Latest version of JAY Login & Register plugin (version higher than 2.6.03)

  1. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  2. Locate the JAY Login & Register plugin
  3. Check the current installed version (vulnerable if 2.6.03 or lower)
  4. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins/jay-login-register/ and upload via Plugins > Add New > Upload Plugin
  5. After updating, verify the new version number reflects a release higher than 2.6.03
  6. Confirm the site still functions correctly by testing user registration and login functionality

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
  • 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-2025-15027 — 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-15027 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