CVE-2025-10762VulnerabilityPublished 21 Sep 2025Updated 22 Sep 2025

CVE-2025-10762: kuaifan DooTask · SQL Injection

Affects kuaifan DooTaskSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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 21 Sep 2025
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-25.

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
kuaifan DooTask	Affected =1.2.0 =1.2.1 =1.2.2 =1.2.3 =1.2.4 =1.2.5 =1.2.6 =1.2.7 =1.2.8 =1.2.9 =1.2.10 =1.2.11 =1.2.12 =1.2.13 =1.2.14 =1.2.15 =1.2.16 =1.2.17 =1.2.18 =1.2.19 =1.2.20 =1.2.21 =1.2.22 =1.2.23 =1.2.24 =1.2.25 =1.2.26 =1.2.27 =1.2.28 =1.2.29 =1.2.30 =1.2.31 =1.2.32 =1.2.33 =1.2.34 =1.2.35 =1.2.36 =1.2.37 =1.2.38 =1.2.39 =1.2.40 =1.2.41 =1.2.42 =1.2.43 =1.2.44 =1.2.45 =1.2.46 =1.2.47 =1.2.48 =1.2.49	Fixed in–

AI-suggested

Immediate mitigation steps include implementing input validation and sanitization on the 'keys[department]' parameter to prevent malicious SQL code execution. Organizations should audit their DooTask installations and restrict external access to the vulnerable API endpoint through network segmentation and firewall rules. Employing Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the affected parameter can provide a temporary protective layer. Monitoring application logs for unusual query patterns or errors related to SQL injection attempts is critical for early detection. Since no official patches are currently available, organizations should engage with the vendor for updates and consider applying virtual patching techniques. Additionally, limiting the privileges of the database user account used by DooTask can reduce the potential impact of exploitation. Regular backups and incident response plans should be reviewed and updated to prepare for potential exploitation scenarios.

Description

A vulnerability was found in kuaifan DooTask up to 1.2.49. Affected by this vulnerability is an unknown functionality of the file app/Http/Controllers/Api/UsersController.php. The manipulation of the argument keys[department] results in sql injection. The attack can be executed remotely. The exploit has been made public and could be used.

Impact

For European organizations utilizing kuaifan DooTask, this vulnerability poses a moderate risk with potential for significant impact. Exploitation could lead to unauthorized access to sensitive user or departmental data, undermining data confidentiality and integrity. This is particularly critical for organizations in regulated sectors such as finance, healthcare, and public administration, where data protection is mandated by GDPR and other regulations. A successful attack could result in data breaches, regulatory penalties, reputational damage, and operational disruptions. Given the remote exploitability and lack of required user interaction, attackers could automate attacks at scale, increasing the risk of widespread compromise. The medium severity score reflects a balance between exploitability and impact; however, the absence of patches and public disclosure heightens the urgency for mitigation. Organizations relying on DooTask for task or user management should be vigilant, as attackers might leverage this vulnerability to pivot within networks or exfiltrate sensitive information.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Sep 2025, 00:45 UTC

Technical details

References

Community reviews

Related threats