Authenticated SQL injection through by parameter
Published Jan 9, 2020 · Updated Aug 5, 2024
SQL injection in user_list.php in SOPlanning 1.45 allows remote authenticated users to alter database queries through the by parameter. The public record identifies the injection point but does not disclose the query construction or input-handling error inside user_list.php. A valid application account is required, and successful exploitation executes attacker-controlled SQL statements against the application database.
Summary
What happened
SQL injection in user_list.php in SOPlanning 1.45 allows remote authenticated users to alter database queries through the by parameter. The public record identifies the injection point but does not disclose the query construction or input-handling error inside user_list.php. A valid application account is required, and successful exploitation executes attacker-controlled SQL statements against the application database.
The record
- CVE
- CVE-2019-20179
- Published
- Jan 9, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 9, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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
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