Unauthenticated SQL injection via unsanitized upload identifier
Published Oct 1, 2026 · Updated Oct 1, 2026
SQL injection in Iptanus File Upload 5.1.10 and earlier allows remote attackers to influence database queries through an upload identifier. The upload workflow does not fully sanitize that identifier before a SQL operation. Exploitation requires a reachable upload workflow; published material does not identify the affected query or establish whether database contents can be read or changed.
Summary
What happened
SQL injection in Iptanus File Upload 5.1.10 and earlier allows remote attackers to influence database queries through an upload identifier. The upload workflow does not fully sanitize that identifier before a SQL operation. Exploitation requires a reachable upload workflow; published material does not identify the affected query or establish whether database contents can be read or changed.
The record
- CVE
- CVE-2026-62071
- Published
- Oct 1, 2026
- Updated
- Oct 1, 2026
- Vendor
- nickboss
- Product
- Iptanus File Upload
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 1, 2026CVE publishedPublication date reported by the CVE source.
- Oct 1, 2026Record 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=n/a <=5.1.10 changes=[{"at":"5.2.0","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started