dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-14250

MEDIUM · 6.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 →
69/100
Remediation priority · Elevated
Remotely reachable 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 Themehunk Login Registration plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.0.2. This is due to the handle_frontend_register() function in the unauthenticated /thlogin/v1/register REST endpoint accepting a user-controlled 'role' parameter and validating it only against get_editable_roles() — which returns every defined editable site role, including 'editor' — before passing it to wp_insert_user(). This makes it possible for unauthenticated attackers, when public user registration is enabled, to create new accounts with the editor role.

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 Themehunk Login Registration plugin for WordPress versions up to 1.0.2 contains a privilege escalation vulnerability in its unauthenticated /thlogin/v1/register REST endpoint. The handle_frontend_register() function accepts a user-controlled 'role' parameter and validates it only against get_editable_roles(), which returns all editable site roles including 'editor', allowing unauthenticated attackers to register accounts with elevated privileges when public user registration is enabled.

MitigationRestrict the allowed roles in handle_frontend_register() to only 'subscriber' (the default WordPress user role), or disable public user registration until a patched version is available.

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

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

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. Identify if Themehunk Login Registration plugin is installed
    Check the WordPress plugins directory for the 'themehunk-login-registration' folder, or query the wp_options table for 'active_plugins', or inspect the file system at /wp-content/plugins/ for the plugin folder
    Affected if The plugin folder exists and the plugin is active in WordPress
  2. Confirm the plugin version
    Inspect the plugin main file header (usually themehunk-login-registration.php) for the 'Version' comment, or query the wp_options table for the option_name containing the plugin version
    Affected if The installed version is 1.0.2 or any lower version number
  3. Verify if public user registration is enabled
    In WordPress admin, go to Settings > General and check 'Membership: Anyone can register', or query the wp_options table for 'users_can_register' option value = 1
    Affected if The 'users_can_register' option is set to 1 (enabled)
  4. Confirm the vulnerable REST endpoint exists
    Inspect the plugin source code for the REST route registration '/thlogin/v1/register' in the init hook, or attempt a HEAD request to /wp-json/thlogin/v1/register
    Affected if The REST endpoint /thlogin/v1/register is registered and accessible without authentication

A user is affected if the Themehunk Login Registration plugin version 1.0.2 or lower is installed, public user registration is enabled, and the vulnerable /thlogin/v1/register REST endpoint is accessible, allowing unauthenticated privilege escalation.

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

Restrict the allowed roles in handle_frontend_register() to only 'subscriber' (the default WordPress user role), or disable public user registration until a patched version is available.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (newer than 1.0.2)

  1. Check the current version of the Themehunk Login Registration plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate Themehunk Login Registration and note the current version
  4. Update the plugin to the latest available version from the WordPress plugin repository
  5. After updating, verify the plugin version has changed and the update was successful
  6. Ensure public user registration settings are reviewed in WordPress under Settings > General > Membership (if enabled)

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-14250 — 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-14250 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