CVE-2026-1884VulnerabilityPublished 4 Feb 2026Updated 23 Feb 2026

CVE-2026-1884: ZenTao · Server-Side Request Forgery

Affects ZenTaoSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
ZenTao	Affected =21.7.6-85642	Fixed in–
GitHubzentao/zentao`pkg:github/zentao/zentao`Other threats	Affected =21.7.6-85642	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-1884, organizations should first upgrade ZenTao to a version that addresses this vulnerability once available. In the absence of an official patch, apply the following measures: 1) Restrict network egress from the ZenTao server to only trusted external endpoints to limit SSRF impact. 2) Implement strict input validation and sanitization on webhook URLs and any user-supplied data to prevent malicious request injection. 3) Employ network segmentation to isolate the ZenTao server from sensitive internal services and metadata endpoints. 4) Monitor logs for unusual outbound requests originating from the ZenTao server, which may indicate exploitation attempts. 5) Limit user privileges within ZenTao to reduce the risk of high-privilege exploitation. 6) Use web application firewalls (WAFs) with SSRF detection capabilities to block suspicious requests. 7) Conduct regular security assessments and penetration testing focusing on SSRF vectors. These targeted mitigations go beyond generic advice by focusing on network controls, input validation, and monitoring specific to the vulnerable component.

Description

A weakness has been identified in ZenTao up to 21.7.6-85642. The impacted element is the function fetchHook of the file module/webhook/model.php of the component Webhook Module. This manipulation causes server-side request forgery. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The SSRF vulnerability in ZenTao can lead to unauthorized internal network access, allowing attackers to probe and interact with internal services that are otherwise inaccessible from the internet. This can expose sensitive information, such as internal APIs, cloud metadata endpoints, or private databases. While the direct impact on confidentiality, integrity, and availability is rated low to medium, the SSRF can serve as a pivot point for more severe attacks, including lateral movement or data exfiltration. Organizations relying on ZenTao for project management may face disruption or data leakage risks if attackers exploit this vulnerability. The lack of vendor response and patches increases the window of exposure. Since exploitation requires high privileges, the threat is more severe in environments where attackers have already gained some level of access, enabling them to escalate privileges or move laterally. The public availability of exploit code raises the risk of opportunistic attacks, especially in organizations with weak internal network segmentation or insufficient monitoring.

Summary

CVE-2026-1884 is a server-side request forgery vulnerability affecting ZenTao, an open-source project management software widely used for agile development and bug tracking. The vulnerability resides in the fetchHook function within the webhook module's model.php file. This function improperly handles external URLs or user-supplied input, allowing an attacker to craft malicious requests that the server then executes internally. SSRF vulnerabilities enable attackers to make arbitrary HTTP requests from the vulnerable server, potentially accessing internal network resources, sensitive metadata services, or other protected endpoints that are not directly accessible externally. The vulnerability affects ZenTao versions up to 21.7.6-85642. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no user interaction (UI:N), but requires high privileges (PR:H), with low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). The exploit code has been publicly released, increasing the risk of exploitation despite no current reports of active attacks. The vendor has not issued any patches or responses, leaving users exposed. This SSRF can be leveraged for reconnaissance, internal network scanning, or accessing internal services, potentially leading to further compromise depending on the internal environment.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:59 UTC

Technical details

References

Community reviews

Related threats