Skip to content
Web

CVE-2026-7106

8.8
High
EPSS 0.31%Apr 27, 2026

Privilege escalation in WordPress plugin allows authenticated users to modify roles

common questions

Is CVE-2026-7106 being exploited?

Not confirmed. CVE-2026-7106 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.

How severe is CVE-2026-7106?

CVE-2026-7106 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-7106?

Not known from our data. No patch reference has been recorded for CVE-2026-7106, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-7106 affect?

CVE-2026-7106 affects WordPress plugin Highland Software Custom Role Manager <=1.0.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-7106?

Disable the plugin or restrict profile updates until patched

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WordPress plugin Highland Software Custom Role Manager <=1.0.0
impact

Authenticated users with Subscriber+ can escalate via profile update, gaining admin-like privileges.

action required

Immediate action required

affected versions
jgrodgers Highland Software Custom Role Manager
  • affected<= 1.0.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free