Database-name disclosure via injected M_Id SQL syntax
Published Aug 18, 2022 · Updated Aug 3, 2024
SQL injection in Library Management System 1.0 allows remote attackers to disclose the database name through the M_Id parameter. /student/dele.php evaluates attacker-controlled M_Id SQL syntax in a database statement, and the error-based updatexml payload returns the database name. No user interaction or privileges are required according to NVD; the published proof demonstrates database-name disclosure rather than broader database or host compromise.
Summary
What happened
SQL injection in Library Management System 1.0 allows remote attackers to disclose the database name through the M_Id parameter. /student/dele.php evaluates attacker-controlled M_Id SQL syntax in a database statement, and the error-based updatexml payload returns the database name. No user interaction or privileges are required according to NVD; the published proof demonstrates database-name disclosure rather than broader database or host compromise.
The record
- CVE
- CVE-2022-36725
- Published
- Aug 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 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.
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- SQLi-15 proof-of-concept requestproof 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