Authenticated SQL injection via unescaped LSS parameter
Published Jul 19, 2024 · Updated Aug 1, 2024
SQL injection in SourceCodester Record Management System 1.0 allows remote authenticated users to alter database queries via LSS. add_leave_non_user.php interpolates the POST value directly into a service_credits INSERT statement without parameterization or escaping. A valid session is required; the published exploit demonstrates boolean- and time-based blind inference, but it does not demonstrate code execution.
Summary
What happened
SQL injection in SourceCodester Record Management System 1.0 allows remote authenticated users to alter database queries via LSS. add_leave_non_user.php interpolates the POST value directly into a service_credits INSERT statement without parameterization or escaping. A valid session is required; the published exploit demonstrates boolean- and time-based blind inference, but it does not demonstrate code execution.
The record
- CVE
- CVE-2024-6906
- Published
- Jul 19, 2024
- Updated
- Aug 1, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Record Management System LSS SQL injection 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