SQL injection via unescaped form and login input
Published Jan 18, 2023 · Updated Aug 7, 2024
SQL injection in Ptome before 2010-01-11 allows attackers to read or modify database data through crafted form or login input. The Field postProcess method stored values without SQLPrep, while LoginManager inserted unescaped username input into a raw SQL query. Database permissions bound the consequences, and published assessments disagree on network reachability and required privileges.
Summary
What happened
SQL injection in Ptome before 2010-01-11 allows attackers to read or modify database data through crafted form or login input. The Field postProcess method stored values without SQLPrep, while LoginManager inserted unescaped username input into a raw SQL query. Database permissions bound the consequences, and published assessments disagree on network reachability and required privileges.
The record
- CVE
- CVE-2010-10009
- Published
- Jan 18, 2023
- Updated
- Aug 7, 2024
- Vendor
- Ptome Project
- Product
- Ptome
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 18, 2023CVE publishedPublication date reported by the CVE source.
- Aug 7, 2024Record 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
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
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo