CVE-2026-4004

The Task Manager plugin for WordPress is vulnerable to arbitrary shortcode execution via the 'search' AJAX action in all versions up to, and including, 3.

Verified by Precogs Threat Research
Last Updated: Mar 21, 2026
Base Score
6.5MEDIUM

Executive Summary

CVE-2026-4004 is a medium severity vulnerability affecting appsec. It is classified as Code Injection. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"This security defect is primarily driven by within The Task Manager plugin, allowing a lack of rigorous type checking mechanisms. This flaw provides a direct pathway for attackers to compromise the entire application stack, rendering traditional defenses ineffective. The Precogs AI's Code Property Graph analysis traces untrusted input to block malicious interactions before they reach production."

Exploit Probability (EPSS)
Low (0.1%)
Public POC
Undisclosed
Exploit Probability
Low (<10%)
Public POC
Available
Affected Assets
appsecCWE-94

What is this vulnerability?

CVE-2026-4004 is categorized as a critical Code Injection / RCE flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

The Task Manager plugin for WordPress is vulnerable to arbitrary shortcode execution via the 'search' AJAX action in all versions up to, and including, 3.0...

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score6.5 (MEDIUM)
Vector StringCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
PublishedMarch 21, 2026
Last ModifiedMarch 21, 2026
Related CWEsCWE-94

Impact on Systems

Remote Code Execution: Attackers achieve arbitrary command execution within the context of the application server.

Privilege Escalation: Initial code execution can be exploited to pivot and elevate privileges across the network.

Persistent Backdoors: Attackers can bind reverse shells, modify source files, or inject persistent access mechanisms.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Remove Dynamic Evaluation Completely eliminate the use of dynamic evaluation functions (eval(), exec(), system()) on untrusted input.

2. Sandboxing If dynamic execution is an absolute business requirement, isolate the execution environment in tightly constrained, non-networked sandboxes (e.g., restricted WebAssembly or isolated containers).

3. Network Segmentation Restrict outbound traffic from the application server (egress filtering) to prevent reverse shell connections.

Vulnerability Signature

// Vulnerable Node.js Execution
const exec = require('child_process').exec;
const user_domain = req.query.domain;
// VULNERABLE: Injecting user input directly into system shell commands
exec('ping -c 4 ' + user_domain, (error, stdout, stderr) =\> \{
    res.send(stdout);
\});

// EXPLOIT PAYLOAD: precogs.ai ; cat /etc/passwd

References and Sources

Vulnerability Code Signature

Attack Data Flow

StageDetail
SourceUntrusted payload via API or file upload
VectorInput passed to a dynamic code evaluation function
Sinkeval(), exec(), or similar unsafe execution sink
ImpactRemote Code Execution (RCE), full system compromise

Vulnerable Code Pattern

# ❌ VULNERABLE: Dynamic code evaluation
def process_data(user_input):
    # Taint sink: arbitrary code execution
    result = eval(user_input)
    return result

Secure Code Pattern

# ✅ SECURE: Safe parsing
import ast
def process_data(user_input):
    # Sanitized parsing: only evaluates literal structures
    result = ast.literal_eval(user_input)
    return result

How Precogs Detects This

Precogs AI Analysis Engine identifies unsafe dynamic code evaluation paths by tracking untrusted data into sinks like eval() and exec().\n

Related Vulnerabilitiesvia CWE-94

Is your system affected?

Precogs AI detects CVE-2026-4004 in compiled binaries, LLMs, and application layers — even without source code access.