Database disclosure and tampering via raw SQL interpolation
Published Sep 21, 2025 · Updated Sep 22, 2025
SQL injection in Hitosea DooTask 1.2.0 through 1.2.49 allows remote authenticated users to read and alter database data. The users-list handler inserts keys[department] directly into a selectRaw EXISTS subquery without parameter binding or validation. A logged-in account and network access to /api/users/lists are required; successful injection exposes database identity and permits data tampering.
Summary
What happened
SQL injection in Hitosea DooTask 1.2.0 through 1.2.49 allows remote authenticated users to read and alter database data. The users-list handler inserts keys[department] directly into a selectRaw EXISTS subquery without parameter binding or validation. A logged-in account and network access to /api/users/lists are required; successful injection exposes database identity and permits data tampering.
The record
- CVE
- CVE-2025-10762
- Published
- Sep 21, 2025
- Updated
- Sep 22, 2025
- Vendor
- DooTask
- Product
- DooTask
- Classifications
- CWE-74, CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 21, 2025CVE publishedPublication date reported by the CVE source.
- Sep 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.2.0
- Affected versionversion=1.2.1
- Affected versionversion=1.2.10
- Affected versionversion=1.2.11
- Affected versionversion=1.2.12
- Affected versionversion=1.2.13
- Affected versionversion=1.2.14
- Affected versionversion=1.2.15
- Affected versionversion=1.2.16
- Affected versionversion=1.2.17
- Affected versionversion=1.2.18
- Affected versionversion=1.2.19
- Affected versionversion=1.2.2
- Affected versionversion=1.2.20
- Affected versionversion=1.2.21
- Affected versionversion=1.2.22
- Affected versionversion=1.2.23
- Affected versionversion=1.2.24
- Affected versionversion=1.2.25
- Affected versionversion=1.2.26
- Affected versionversion=1.2.27
- Affected versionversion=1.2.28
- Affected versionversion=1.2.29
- Affected versionversion=1.2.3
- Affected versionversion=1.2.30
- Affected versionversion=1.2.31
- Affected versionversion=1.2.32
- Affected versionversion=1.2.33
- Affected versionversion=1.2.34
- Affected versionversion=1.2.35
- Affected versionversion=1.2.36
- Affected versionversion=1.2.37
- Affected versionversion=1.2.38
- Affected versionversion=1.2.39
- Affected versionversion=1.2.4
- Affected versionversion=1.2.40
- Affected versionversion=1.2.41
- Affected versionversion=1.2.42
- Affected versionversion=1.2.43
- Affected versionversion=1.2.44
- Affected versionversion=1.2.45
- Affected versionversion=1.2.46
- Affected versionversion=1.2.47
- Affected versionversion=1.2.48
- Affected versionversion=1.2.49
- Affected versionversion=1.2.5
- Affected versionversion=1.2.6
- Affected versionversion=1.2.7
- Affected versionversion=1.2.8
- Affected versionversion=1.2.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue sqlmap proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo