Database disclosure via inventory id SQL injection
Published Jun 17, 2022 · Updated Aug 3, 2024
SQL injection in Online Ordering System 2.3.2 allows remote authenticated users to read database data through the inventory edit id parameter. The inventory edit handler incorporates the id query value into a database query without neutralizing SQL syntax, enabling UNION SELECT input. The public proof of concept sends a PHP session cookie to the admin route and demonstrates disclosure of the current database name.
Summary
What happened
SQL injection in Online Ordering System 2.3.2 allows remote authenticated users to read database data through the inventory edit id parameter. The inventory edit handler incorporates the id query value into a database query without neutralizing SQL syntax, enabling UNION SELECT input. The public proof of concept sends a PHP session cookie to the admin route and demonstrates disclosure of the current database name.
The record
- CVE
- CVE-2022-31357
- Published
- Jun 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 17, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- SQLi-3 proof of conceptproof of concept · 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