Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | This vulnerability presents substantial real-world risk despite a moderate CVSS v4.0 score of 6.9. The CVSS vector confirms unauthenticated remote attack (AV:N, PR:N, UI:N), no complexity requirements (AC:L), and limited immediate confidentiality/integrity impact in the base vector (VC:L, VI:L, VA:L). However, the RCE/Code Injection tags and CWE-94 classification indicate the actual technical impact is complete system compromise-the low impact ratings in CVSS v4.0 appear to reflect conservative scoring rather than the severity of code execution. The SSVC decision framework rates Exploitation as 'none' (no confirmed active exploitation), Automatable as 'no' (requires crafted payload), and Technical Impact as 'partial,' which aligns with the moderate CVSS but underestimates post-exploitation risk. The lack of vendor response to early disclosure and the presence of three consecutive vulnerable versions (5.1.0-5.1.2) suggest prolonged exposure risk in production environments. Organizations running PowerJob should treat this as a critical patch-now priority despite the 6.9 CVSS, as unauthenticated RCE via code injection is a foundational attack surface. |
| Exploit ScenarioDerived | An attacker discovers a PowerJob instance running version 5.1.0-5.1.2 exposed on a public IP or internal network. The attacker crafts an HTTP POST request to /openApi/addWorkflowNode with a malicious Groovy expression embedded in the nodeParams argument, such as code that instantiates a ProcessBuilder to execute shell commands. Since no authentication is required (PR:N) and the endpoint directly passes nodeParams to GroovyEvaluator.evaluate(), the malicious code executes on the server with the privileges of the PowerJob process-typically application-level or service account privileges. The attacker could then establish reverse shell access, steal secrets from the job scheduler, or pivot to downstream systems depending on network segmentation. No public exploit code has been confirmed, but the attack surface is straightforward and requires only standard HTTP tooling to execute. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 07, 2026
Remote code injection in PowerJob 5.1.0, 5.1.1, and 5.1.2 allows unauthenticated attackers to execute arbitrary code via the GroovyEvaluator.evaluate function in the OpenAPI endpoint /openApi/addWorkflowNode by manipulating the nodeParams argument. The vulnerability exploits unsafe Groovy code evaluation without input sanitization, enabling full remote code execution with a low CVSS complexity score (6.9/10). No public exploit code is confirmed at time of analysis, and the vendor has not yet responded to the early disclosure notification.
RemediationAI
No vendor-released patch identified at time of analysis. The vendor has not yet responded to the early disclosure notification provided through GitHub issue #1168. Organizations should monitor the PowerJob GitHub repository and release page (https://github.com/PowerJob/PowerJob/) for patched versions (expected at 5.1.3 or higher once available). Immediate interim mitigations include: (1) Network isolation-restrict access to the /openApi/addWorkflowNode endpoint using firewall rules or WAF policies to trusted internal networks only; (2) Authentication layer-deploy API gateway authentication (OAuth2, mTLS, API keys) in front of PowerJob if not natively available; (3) Input validation-review and restrict nodeParams to non-executable schemas if possible through application-level hardening. Upgrade immediately upon availability of a patched release.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in maven, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
PowerJob is a distributed job scheduler framework that uses Groovy script evaluation for workflow automation. The vulnerability exists in the GroovyEvaluator component, which dynamically evaluates Groovy code passed through the nodeParams parameter of the /openApi/addWorkflowNode REST endpoint. This is a classic unsafe deserialization/code injection pattern (CWE-94: Improper Control of Generation of Code) where user-supplied data is directly executed as code without validation, compilation safety checks, or sandboxing. Groovy's eval() or similar dynamic execution methods can instantiate arbitrary Java objects and invoke methods, granting attackers direct access to the JVM runtime. The OpenAPI endpoint's lack of authentication (PR:N in CVSS v4.0) means the vulnerable function is callable by any network-accessible client.
Know when Powerjob 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Primary rating from Vendor (VulDB) · only source for this CVE.
CVSS VectorVendor: VulDB
DescriptionCVE.org
A security flaw has been discovered in PowerJob 5.1.0/5.1.1/5.1.2. The affected element is the function GroovyEvaluator.evaluate of the file /openApi/addWorkflowNode of the component OpenAPI Endpoint. The manipulation of the argument nodeParams results in code injection. The attack can be executed remotely. The project was informed of the problem early through an issue report but has not responded yet.
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
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
PowerJob v4.3.3 was discovered to contain a remote command execution (RCE) vulnerability via the instanceId parameter at
Unauthenticated remote code execution in PowerJob Worker 5.1.2 (and likely earlier) stems from the /worker/deployContain
Unauthenticated remote code execution in PowerJob 4.x through 5.1.2 lets any actor that can reach the server's Server-Wo
Powerjob >= 3.20 is vulnerable to SQL injection via the version parameter. Rated critical severity (CVSS 9.8), this vuln
PowerJob V4.3.1 is vulnerable to Incorrect Access Control that allows for remote code execution. Rated critical severity
PowerJob V4.3.2 has unauthorized interface that causes remote code execution. Rated critical severity (CVSS 9.8), this v
Missing authorization in PowerJob through 5.1.2 exposes the /user/list endpoint, allowing remote unauthenticated attacke
PowerJob V4.3.1 is vulnerable to Incorrect Access Control via the create user/save interface. Rated medium severity (CVS
PowerJob V4.3.1 is vulnerable to Insecure Permissions. Rated medium severity (CVSS 5.3), this vulnerability is remotely
PowerJob V4.3.1 is vulnerable to Incorrect Access Control via the create app interface. Rated medium severity (CVSS 5.3)
Remote code execution in PowerJob Server 5.1.2 (and likely earlier releases) stems from a predictable/hardcoded HS256 si
An incorrect access control vulnerability in powerjob 4.3.2 and earlier allows remote attackers to obtain sensitive info
EUVD-2026-19896
GHSA-wpwf-v25w-54g3
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB