dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-7106

HIGH · 8.8 CVSS v3.1 Published 2026-04-27
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 Highland Software Custom Role Manager plugin for WordPress is vulnerable to Privilege Escalation in versions up to and including 1.0.0. This is due to insufficient authorization checks in the hscrm_save_user_roles() function, which is hooked to the personal_options_update action accessible by any authenticated user. This makes it possible for authenticated attackers, with Subscriber-level access or higher, to potentially modify user roles via the profile update form.

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 Highland Software Custom Role Manager WordPress plugin (versions up to 1.0.0) contains a privilege escalation vulnerability due to missing authorization checks in the hscrm_save_user_roles() function. This function is hooked to the personal_options_update action and accepts user role modifications from any authenticated user with Subscriber-level access or higher, allowing attackers to escalate their own privileges or modify other users' roles.

MitigationUpgrade to a version newer than 1.0.0 where the vulnerability is patched. If no update is available, implement proper capability checks and nonce verification in the hscrm_save_user_roles() function to ensure only authorized administrators can modify user roles.

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 plugin installation
    Check the WordPress plugins directory for the Highland Software Custom Role Manager plugin folder, typically at wp-content/plugins/, or query the wp_options table for the active_plugins option to list installed plugins.
    Affected if The plugin folder named 'highland-software-custom-role-manager', 'hscrm', or similar containing 'custom role manager' is present in the plugins directory or listed in active_plugins.
  2. Identify installed version
    Read the plugin's main PHP file header (usually named index.php or highland-software-custom-role-manager.php) to find the Version: field, or query the wp_options table for the option_name containing the plugin version.
    Affected if The Version field shows 1.0.0 or any version lower than a patched release (the vulnerability affects versions up to and including 1.0.0).
  3. Verify vulnerable function exists
    Search the plugin's PHP files for the function definition 'function hscrm_save_user_roles()' or grep for this string in the plugin directory.
    Affected if The function hscrm_save_user_roles is defined within the plugin files, indicating the vulnerable code is present.
  4. Confirm hook registration
    Search the plugin files for 'add_action' with 'personal_options_update' hook, or examine the plugin's main file for action hooks registered during initialization.
    Affected if The code contains 'add_action(\'personal_options_update\', \'hscrm_save_user_roles\')' or similar, enabling the vulnerable function to trigger on profile updates.
  5. Check for subscriber-level users
    Query the wp_users and wp_usermeta tables, or use the WordPress admin dashboard to list users and their assigned roles.
    Affected if Any user account exists with the Subscriber role or higher, allowing authenticated access to the profile update form where the vulnerable function can be triggered.

A user is affected if the Highland Software Custom Role Manager plugin (version 1.0.0 or lower) is installed and active, with the vulnerable hscrm_save_user_roles function hooked to personal_options_update, and at least one authenticated user with Subscriber-level access exists in the WordPress installation.

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

Upgrade to a version newer than 1.0.0 where the vulnerability is patched. If no update is available, implement proper capability checks and nonce verification in the hscrm_save_user_roles() function to ensure only authorized administrators can modify user roles.

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-2026-7106 — 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-7106 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