Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running Taskbot <=6.6
-
DeliverySend crafted unauthenticated request
-
ExploitTrigger improper privilege assignment
-
ExecutionObtain administrator account
-
PersistUpload malicious plugin/webshell
-
ImpactFull site compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Privilege assignment review
|
| Exploitation Conditions | The target must be a WordPress installation with the Amentotech Taskbot plugin installed and activated at version 6.6 or earlier; the vulnerable privilege-assignment logic is reachable in the plugin's default state. Per the CVSS vector (PR:N/UI:N/AC:L) and the 'Unauthenticated' description, no credentials, no victim interaction, and no special non-default configuration are required - remote unauthenticated exploitation works against a standard install. The principal limiting factor is deployment scope: exploitation is confined to sites running this specific, relatively uncommon plugin, so exposure depends entirely on the plugin being present rather than on any additional precondition. |
| Impact | All provided signals point to a high-severity, high-priority flaw, though confidence is tempered by sparse corroborating intelligence. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated vulnerability yielding full C:H/I:H/A:H impact - consistent with the 'Unauthenticated Privilege Escalation' description and CWE-266 (Incorrect Privilege Assignment), where an attacker gains administrator-level WordPress access without credentials. No EPSS score, SSVC decision, KEV listing, or POC reference was supplied, so exploitation likelihood cannot be quantified from the input: there is no public exploit identified at time of analysis and no evidence of active exploitation. The absence of EPSS/KEV data does not lower the intrinsic severity - a full-admin takeover primitive in a WordPress plugin is highly attractive and such flaws are frequently weaponized quickly once disclosed - but it does mean the 'real-world exploitation probability' leg of the assessment is unknown rather than low. Net: a genuine priority for anyone running the affected plugin, driven by the unauthenticated-to-admin impact, with the caveat that exploitation telemetry (EPSS/KEV/POC) is missing and the underlying product is niche, limiting aggregate blast radius. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends a crafted HTTP request to a WordPress site running the Taskbot plugin (version 6.6 or earlier), abusing an improperly protected privilege-assignment function to grant themselves administrator-level access. With admin rights, they install a malicious plugin or PHP webshell to achieve full remote code execution and site takeover. No public exploit code was identified in the provided data; the low attack complexity (AC:L) and lack of required privileges or user interaction make exploitation straightforward once a working request is constructed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Unauthenticated privilege escalation in the Amentotech Taskbot plugin for WordPress (versions 6.6 and earlier) allows any remote attacker to elevate privileges on a vulnerable site without credentials or victim interaction, as reflected by the CVSS 3.1 vector PR:N/UI:N/AC:L and a 9.8 base score. Because the flaw sits in privilege-assignment logic that is reachable in the plugin's default configuration, a standard installation that simply has Taskbot active is exposed; the practical limiting factor is that exposure depends entirely on this relatively uncommon plugin being deployed. There is confirmed actively exploited status absent - no CISA KEV entry was provided - and no public exploit code was identified in the supplied intelligence at time of analysis, so this should be prioritized on the basis of severity and ease of exploitation rather than observed attacks, with the caveat that corroborating intelligence is sparse and comes primarily from the Patchstack report.
RemediationAI
No vendor-released patch was identified in the available intelligence at time of analysis, so the primary action is exposure removal: deactivate and, if the site's functionality permits, fully uninstall the Amentotech Taskbot plugin until a fixed release is published - the trade-off is loss of the task-marketplace features the plugin provides, so sites that must keep it should treat this as a temporary, risk-accepted gap on an isolated deployment. Where the plugin must remain active, restrict the attack surface by blocking unauthenticated requests to the plugin's role/user-assignment handling (its AJAX/admin-ajax, REST, and registration/form endpoints) at the WAF or reverse proxy, allowing only expected sources such as authenticated administrators; the side effect is that legitimate front-end workflows (user sign-up, role selection, provider onboarding) may break, so test the rule set against normal traffic. Additionally, audit existing WordPress users for unexpected administrator or elevated-role accounts created since the plugin was installed, rotate administrator credentials and salts, enable alerting on wp_users/wp_usermeta role changes, and monitor the Patchstack advisory page at https://patchstack.com/database/wordpress/plugin/taskbot/vulnerability/wordpress-taskbot-plugin-6-6-privilege-escalation-vulnerability?_s_id=cve for an updated fixed version before restoring the plugin in production.
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
The vulnerability is an Incorrect Privilege Assignment (CWE-266) in the Amentotech Taskbot WordPress plugin, a theme/plugin suite used for on-demand task and service marketplaces. CWE-266 covers cases where an application grants a privilege, role, or capability level that the requesting principal should not receive - here the plugin's role/user-assignment handling can be driven by an unauthenticated HTTP request, so a remote attacker can cause the site to grant elevated rights (for example an administrative or otherwise privileged WordPress role) without ever authenticating. The CPE entry cpe:2.3:a:amentotech:taskbot:*:*:*:*:*:*:*:* confirms the vendor/product scope covers all released Taskbot versions at or below the affected threshold, and the CVSS vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H describes a network-reachable, low-complexity, unauthenticated path with high confidentiality, integrity, and availability impact confined to the WordPress instance itself. The WordPress plugin ecosystem is a common source of this root-cause class because registration, role-selection, and AJAX/REST handlers frequently trust client-supplied role parameters; the assessment notes the vulnerable logic is reachable in the plugin's default state, meaning no non-default setting must be enabled for exploitation.
Know when Taskbot 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:N/UI:N/S:U/C:H/I:H/A:H
Unauthenticated (PR:N), network-reachable (AV:N) privilege escalation to WordPress admin with no user interaction (AC:L/UI:N) grants full control, so C/I/A all High.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Privilege Escalation in Taskbot <= 6.6 versions.
Articles & Coverage 1
Executive ViewAI
Any organization that runs the Amentotech Taskbot plugin (version 6.6 or earlier) on a WordPress site is exposed to full site takeover, because an unauthenticated attacker can grant themselves administrative privileges without credentials or any action by a user. Leadership should care because a compromised public-facing website can be repurposed to host malware, deface brand properties, and expose customer or employee data, and the exposure window stays open indefinitely since no vendor fix is available. The risk is concentrated rather than universal - only sites with this specific plugin deployed are affected - so a rapid inventory and removal decision is the single most decisive action available.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate and remove the Amentotech Taskbot plugin (version 6.6 or earlier) from all WordPress installations; where removal is not immediately possible, take the affected site offline or restrict access via an authenticating reverse proxy; apply WAF or reverse-proxy virtual patching to block unauthenticated requests to the plugin's endpoints, admin-ajax.php, and associated REST routes; audit WordPress user accounts for unauthorized administrator creation and review logs for privilege-assignment activity; rotate administrator credentials, database passwords, and WordPress authentication salts on any site that ran the plugin.
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-93262
GHSA-6p8p-m5mv-926w
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB