dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-15100

HIGH · 8.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 →
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 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_panel_ajax_update_profile' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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) contains a privilege escalation vulnerability in the 'jay_panel_ajax_update_profile' function. This function improperly allows authenticated users with Subscriber-level access to update arbitrary user metadata, enabling attackers to modify their own user role to administrator and gain full site control.

MitigationUpdate the plugin to the latest version once available; if no patch exists, disable or remove the plugin and audit user accounts for unauthorized privilege 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
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. Confirm the JAY Login & Register plugin is installed
    Navigate to WordPress admin > Plugins and look for 'JAY Login & Register' in the list of installed plugins, or check the /wp-content/plugins/ directory for a folder named 'jay-login-register' or similar
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In the WordPress Plugins admin page, click on the plugin name to view its details, or open the main plugin file (usually jay-login-register.php or similar in the plugin folder) and look for the 'Version:' header in the plugin comments
    Affected if The version number is 2.6.03 or lower (any version 'up to 2.6.03' is affected)
  3. Verify the vulnerable function exists in the codebase
    Using a file manager or grep search in the plugin directory, search for the string 'jay_panel_ajax_update_profile' in PHP files
    Affected if The function is found in the plugin code, indicating the vulnerable code is present
  4. Check for subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the list for accounts with the 'Subscriber' role; also check user metadata for any unexpected role assignments
    Affected if There are subscriber accounts present in the system (these could be exploited)
  5. Audit user accounts for unauthorized privilege escalation
    Review the user table or user profile list, checking the 'Role' column for any accounts that were modified to Administrator level unexpectedly, or check wp_usermeta for changes in_cap and wp_capabilities fields
    Affected if Any user account shows a role change to Administrator that was not authorized or expected

A user is affected if the JAY Login & Register plugin versions up to 2.6.03 is installed and the vulnerable jay_panel_ajax_update_profile function exists, especially if there are subscriber accounts that could be exploited to gain administrator access.

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 the plugin to the latest version once available; if no patch exists, disable or remove the plugin and audit user accounts for unauthorized privilege changes.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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