CVE-2026-34901
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 · uneditedUnauthenticated Privilege Escalation in iControlWP <= 5.5.3 versions.
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 · moderate confidenceUnauthenticated privilege escalation vulnerability in iControlWP plugin versions 5.5.3 and below allows remote attackers to gain elevated administrative privileges without any authentication credentials.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate iControlWP plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'icontrolwp' or search for files containing 'icontrolwp' in the plugin directoryAffected if The iControlWP plugin folder exists on the server
-
Identify installed iControlWP versionOpen the main plugin file (typically icontrolwp.php or index.php inside the icontrolwp folder) and locate the version comment header, or check the plugin metadata via WordPress admin under Plugins > Installed PluginsAffected if The reported version is 5.5.3 or any version lower than 5.5.3
-
Verify plugin activation statusLog into WordPress admin and navigate to Plugins > Installed Plugins, or query the wp_options table for the option_name 'active_plugins' to see if icontrolwp/icontrolwp.php is in the active plugins listAffected if The iControlWP plugin appears as active or is present in the active_plugins array
-
Confirm vulnerability exposureSince this is an unauthenticated privilege escalation, no authentication bypass test is required. The vulnerability is present if Steps 1-3 confirm: (a) iControlWP is installed, (b) version is 5.5.3 or below, and (c) plugin is active on the siteAffected if All three conditions are true: iControlWP is installed, version is 5.5.3 or below, and the plugin is currently active
If iControlWP plugin version 5.5.3 or below is installed and active on the WordPress site, the environment is vulnerable to unauthenticated privilege escalation and attackers can gain administrative access without credentials.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate iControlWP to the latest version immediately. If no patched version is available, disable the plugin and implement alternative access controls until a fix is released.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34901 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34901 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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