CVE-2026-34901: Privilege Escalation in iControlWP
Platform
wordpress
Component
worpit-admin-dashboard-plugin
Fixed in
5.5.4
CVE-2026-34901 is a critical Privilege Escalation vulnerability affecting the iControlWP plugin for WordPress. An unauthenticated attacker can exploit this flaw to elevate their privileges to that of a WordPress administrator, granting them full control over the site. This vulnerability impacts versions of iControlWP up to and including 5.5.3, and a patch is available in version 5.5.4.
Detect this CVE in your project
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Impact and Attack Scenarios
Successful exploitation of CVE-2026-34901 allows an attacker to bypass authentication and directly assume administrator privileges on a WordPress site. This grants them complete control, including the ability to install malicious plugins, modify themes, steal sensitive data (user credentials, customer information, financial data), deface the website, and potentially pivot to other systems on the network. The blast radius extends to all data and functionality accessible through the WordPress installation. Given the widespread use of WordPress and the plugin's management capabilities, this vulnerability poses a significant risk to a large number of websites.
Exploitation Context
CVE-2026-34901 has been published relatively recently (2026-04-07), and its EPSS score is likely to be assessed as medium to high due to the critical CVSS score and the ease of exploitation (unauthenticated). Public proof-of-concept (POC) code is likely to emerge, increasing the risk of widespread exploitation. Monitor security advisories and threat intelligence feeds for any indications of active exploitation campaigns targeting iControlWP.
Threat Intelligence
Exploit Status
CVSS Vector
What do these metrics mean?
- Attack Vector
- Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
- Attack Complexity
- Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
- Privileges Required
- None — unauthenticated. No login or credentials needed to exploit.
- User Interaction
- None — attack is automatic and silent. Victim does nothing: no click, no file open.
- Scope
- Unchanged — impact is limited to the vulnerable component itself.
- Confidentiality
- High — complete confidentiality loss. Attacker can read all data: credentials, keys, personal data.
- Integrity
- High — attacker can write, modify, or delete any data: databases, config files, or code.
- Availability
- High — complete crash or resource exhaustion. Full denial of service.
Affected Software
Weakness Classification (CWE)
Timeline
- Published
- Modified
Mitigation and Workarounds
The primary mitigation for CVE-2026-34901 is to immediately upgrade the iControlWP plugin to version 5.5.4 or later. If upgrading is not immediately feasible due to compatibility issues or breaking changes, consider temporarily disabling the iControlWP plugin to reduce the attack surface. While a direct WAF rule is unlikely to be effective against privilege escalation, implementing strict access controls and regularly auditing user permissions can help limit the impact of a successful breach. After upgrading, verify the fix by attempting to access administrative functions without proper authentication; successful access indicates the vulnerability persists.
How to fix
Update to version 5.5.4, or a newer patched version
Frequently asked questions
What is CVE-2026-34901 — Privilege Escalation in iControlWP?
CVE-2026-34901 is a critical vulnerability in the iControlWP WordPress plugin allowing unauthenticated attackers to gain administrator privileges. This means an attacker can take complete control of the WordPress site without needing a username or password.
Am I affected by CVE-2026-34901 in iControlWP?
Yes, if you are using iControlWP version 5.5.3 or earlier, you are vulnerable. Check your plugin version using wp plugin list and upgrade immediately.
How do I fix CVE-2026-34901 in iControlWP?
Upgrade the iControlWP plugin to version 5.5.4 or later. If immediate upgrade is not possible, temporarily disable the plugin to reduce your risk.
Is CVE-2026-34901 being actively exploited?
While no active exploitation has been publicly confirmed, the vulnerability's critical severity and ease of exploitation suggest it is likely to be targeted. Monitor security advisories and threat intelligence.
Where can I find the official iControlWP advisory for CVE-2026-34901?
Refer to the iControlWP website and WordPress plugin repository for the latest security advisory and update information: [https://www.icontrolwp.com/](https://www.icontrolwp.com/)
Is your project affected?
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Detect this CVE in your project
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Scan your WordPress project now — no account
Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.
Drag & drop your dependency file
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...