Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain Subscriber credentials
-
DeliveryAccess wp-admin/profile.php
-
ExploitIntercept profile update POST request
-
InstallInject hscrm_user_roles parameter with 'administrator' value
-
C2Submit modified request
-
ExecuteGain Administrator role
-
ImpactInstall malicious plugin or execute arbitrary PHP
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the Highland Software Custom Role Manager plugin version 1.0.0 or earlier to be installed and activated on the target WordPress site. The attacker must possess valid credentials for any authenticated user role-Subscriber, Contributor, Author, Editor, or Administrator-though the vulnerability's significance lies in Subscriber-level accounts being sufficient. WordPress sites with user registration disabled still face risk if any existing low-privilege account is compromised. The personal_options_update action hook fires on all profile updates in WordPress core, making this vulnerability exploitable on default WordPress configurations without requiring non-standard settings. No special plugin configurations, server-side conditions, or WordPress multisite requirements exist-any standard WordPress installation with the plugin active is vulnerable through the standard profile update form accessible at /wp-admin/profile.php. |
| Impact | CVSS 8.8 (AV:N/AC:L/PR:L/UI:N) accurately reflects the technical severity: network-accessible, low complexity, requiring only low privileges (Subscriber account) with no user interaction needed. The attack provides complete scope for confidentiality, integrity, and availability compromise since WordPress Administrator role grants full site control including plugin installation, theme modification, and database access. However, real-world risk depends heavily on deployment context. Exploitation requires an existing authenticated account, limiting impact to sites with open registration or compromised Subscriber credentials. The absence of CISA KEV status and lack of provided EPSS score suggests this is not yet widely exploited in the wild, likely due to the plugin's limited installation base compared to major WordPress plugins. Organizations running this specific plugin face CRITICAL risk since any low-privilege account becomes an instant admin. Those not using Highland Software Custom Role Manager face zero risk despite the high CVSS-this is a targeted plugin vulnerability, not a WordPress core issue. |
| Exploit ScenarioDerived | An attacker registers a free Subscriber account on a WordPress site running the vulnerable plugin (or compromises an existing low-privilege account via credential stuffing). They navigate to their profile page at wp-admin/profile.php and intercept the profile update request using browser developer tools or a proxy like Burp Suite. The attacker adds a manipulated hscrm_user_roles parameter to the POST request, setting their role to 'administrator'. When they submit the profile update, hscrm_save_user_roles() processes the role change without verifying current_user_can('edit_users'), instantly granting full administrative privileges. The attacker now controls the entire WordPress installation, can install backdoor plugins, exfiltrate data, or deface the site. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 27, 2026
Authenticated attackers with Subscriber-level privileges can escalate to Administrator role in Highland Software Custom Role Manager for WordPress via profile update exploitation. The hscrm_save_user_roles() function lacks capability checks on the personal_options_update hook, allowing low-privilege users to modify arbitrary user roles including their own. Version 1.0.1 released with authorization fixes. CVSS 8.8 reflects high impact across confidentiality, integrity, and availability. EPSS data not provided, no CISA KEV listing identified, indicating limited widespread exploitation despite the severity of self-service privilege escalation to site administrator.
RemediationAI
Upgrade immediately to Highland Software Custom Role Manager version 1.0.1, which implements authorization checks in user-ui.php line 203 and related functions per the plugin repository diff at https://plugins.trac.wordpress.org/browser/highland-software-custom-role-manager/tags/1.0.1/includes/user-ui.php#L203. If immediate upgrade is not possible, disable the Highland Software Custom Role Manager plugin entirely until patching-this removes all role management functionality but eliminates the privilege escalation vector. For sites requiring role management during the interim, switch to established alternatives like User Role Editor or Members plugins that have mature security track records. Audit all user accounts for unexpected role changes by reviewing WordPress user lists for Subscribers or Contributors who gained Administrator privileges since plugin installation. Check wp_usermeta table for role modifications if forensic investigation is needed. Do not attempt to patch the vulnerability manually by editing plugin files, as this creates maintenance debt and may be overwritten by auto-updates.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
WordPress action hooks like personal_options_update trigger when any authenticated user updates their profile. The vulnerability stems from CWE-269 (Improper Privilege Management) where the plugin's hscrm_save_user_roles() function processes role modification requests without verifying the current_user_can('edit_users') or similar capability checks. In WordPress's privilege model, Subscribers (the lowest authenticated role) can access profile updates but should never modify user roles-a permission reserved for Administrators. The affected CPE (cpe:2.3:a:jgrodgers:highland_software_custom_role_manager) identifies this as a third-party WordPress plugin by developer jgrodgers. Source code references point to user-ui.php lines 203, 223, and 289 in version 1.0.0 where the vulnerable function hooks into WordPress core actions without proper authorization gates.
Know when Highland Software Custom Role Manager gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
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.
Executive ViewAI
Highland Software Custom Role Manager for WordPress (versions prior to 1.0.1) contains a privilege escalation vulnerability allowing authenticated subscribers to elevate themselves to administrator, granting unrestricted control over site content, user management, and system configuration. Organizations using this plugin face immediate risk of unauthorized administrative access and potential site compromise, requiring urgent patching to prevent insider and account-takeover attacks.
Vendor-released patch: version 1.0.1 includes authorization checks on the personal_options_update hook. If immediate patching is not feasible, disable the Custom Role Manager plugin until update is available; restrict plugin access to trusted administrators only via file permissions (chmod 644); monitor user_meta database changes for unauthorized role modifications; implement Web Application Firewall rules to restrict profile update requests from low-privilege users.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
EUVD-2026-25769
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB