VulnerabilityPublished 16 Mar 2026

CVE-2026-4284: taoofagi easegen-admin · Server-Side Request Forgery

Affects taoofagi easegen-adminSource CVE Database V5

Compare

Public exploit available · CVSS 5.1 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.1Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% 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 16 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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
taoofagieasegen-admin	Affected =8f87936ac774065b92fb20aab55b274a6ea76433	Fixed in–

AI-suggested

To mitigate CVE-2026-4284, organizations should first conduct an immediate audit of all instances of taoofagi easegen-admin to identify affected versions or commits. Given the absence of official patches, implement strict network segmentation and firewall rules to restrict the server's outbound HTTP requests to only trusted destinations, minimizing the SSRF attack surface. Employ application-layer filtering or web application firewalls (WAFs) that can detect and block suspicious SSRF patterns, especially targeting the downloadFile function or related endpoints. Review and harden access controls to ensure only trusted, high-privilege users can invoke vulnerable functionality. If possible, modify or patch the source code internally to validate and sanitize the 'url' parameter rigorously, rejecting any requests to internal IP ranges or unauthorized domains. Monitor logs for unusual outbound requests originating from the server. Additionally, consider deploying runtime application self-protection (RASP) tools to detect and prevent SSRF exploitation attempts in real time. Maintain close monitoring of vendor communications for any future patches or updates and prepare to apply them promptly.

Description

CVE-2026-4284 is a server-side request forgery (SSRF) vulnerability in the taoofagi easegen-admin product, specifically in the downloadFile function of the PPT File Handler component. The vulnerability arises from improper validation of the 'url' argument, allowing attackers to manipulate requests initiated by the server. Exploitation can be performed remotely without user interaction but requires high privileges on the system. The vulnerability has a medium severity with a CVSS score of 5.1. No patches or updated versions are currently available due to the product's rolling release model and lack of vendor response. While no known exploits are reported in the wild, the public disclosure increases the risk of exploitation. Organizations using this product should prioritize mitigation to prevent potential SSRF attacks that could lead to unauthorized internal network access or data exposure.

Impact

The SSRF vulnerability in taoofagi easegen-admin could allow attackers with high privileges to coerce the server into making unauthorized requests to internal or external systems. This can lead to several impacts including unauthorized access to internal network resources that are otherwise inaccessible externally, exposure of sensitive information, and potential pivoting to further attacks within the network. Organizations using this software in sensitive environments risk data breaches or disruption of internal services. Since the vulnerability requires high privileges, the initial compromise vector might be limited, but once exploited, it can facilitate lateral movement or data exfiltration. The lack of vendor response and patch availability increases the window of exposure, especially in environments where this software is critical. The rolling release nature complicates patch management and vulnerability tracking, potentially leading to inconsistent protection across deployments. Overall, the vulnerability poses a moderate risk to confidentiality and integrity, with limited direct impact on availability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Mar 2026, 01:06 UTC

Technical details

References

Community reviews

Related threats