VulnerabilityPublished 9 Feb 2026Updated 23 Feb 2026

CVE-2026-2226: DouPHP · Unrestricted Upload

Affects DouPHPSource CVE Database V5

Public exploit available · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 11:07 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 35% 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 9 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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
DouPHP	Affected 1.0 – 1.9 10 affected builds	Fixed in–

CPE configurations (1)

cpe:2.3:a:douphp:douphp:*:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2026-2226, organizations should first verify if they are running affected versions of DouPHP (1.0 through 1.9). Since no official patches are referenced, administrators should consider the following specific actions: 1) Restrict access to the /admin/file.php endpoint by IP whitelisting or VPN-only access to reduce exposure. 2) Implement strict server-side validation and sanitization of the sql_filename parameter to ensure only expected file types and names are accepted. 3) Disable or limit file upload functionality if not essential, or replace it with a secure alternative that enforces file type and size restrictions. 4) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious upload attempts targeting this endpoint. 5) Monitor server logs for unusual file upload activity or unexpected file creations in web directories. 6) Isolate the web server environment with least privilege principles to limit the impact of any uploaded malicious files. 7) Regularly back up website data and configurations to enable recovery in case of compromise. 8) Stay alert for official patches or updates from DouPHP developers and apply them promptly when available. 9) Conduct penetration testing or vulnerability scanning focused on file upload mechanisms to identify residual risks.

Description

A vulnerability has been found in DouPHP up to 1.9. This issue affects some unknown processing of the file /admin/file.php of the component ZIP File Handler. Such manipulation of the argument sql_filename leads to unrestricted upload. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Impact

The unrestricted file upload vulnerability in DouPHP can have significant impacts on affected organizations. Successful exploitation allows attackers to upload arbitrary files, including malicious scripts or web shells, which can lead to remote code execution. This compromises the confidentiality of sensitive data stored or processed by the affected system, the integrity of website content or backend data, and the availability of services if attackers disrupt operations or deploy ransomware. Organizations relying on DouPHP for web content management may face defacement, data breaches, or full server compromise. The medium CVSS score reflects moderate ease of exploitation and partial impact, but the real-world impact could escalate if attackers chain this vulnerability with others. Since the attack can be launched remotely without user interaction, the attack surface is broad, increasing risk. The absence of known active exploits reduces immediate threat but does not eliminate future risk. Organizations in regions with higher DouPHP adoption are more likely to be targeted, especially if they lack robust network defenses or monitoring.

References

Community reviews

Loading reviews…