Database-name disclosure via injectable book identifier
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 bookId in /staff/delete.php. The endpoint accepts SQL syntax in the POSTed bookId value and executes an error-based updatexml expression that returns the active database name. NVD assesses no privileges or user interaction are required, although the published request includes a PHP session cookie, leaving session-state dependence unresolved.
Summary
What happened
SQL injection in Library Management System 1.0 allows remote attackers to disclose the database name through bookId in /staff/delete.php. The endpoint accepts SQL syntax in the POSTed bookId value and executes an error-based updatexml expression that returns the active database name. NVD assesses no privileges or user interaction are required, although the published request includes a PHP session cookie, leaving session-state dependence unresolved.
The record
- CVE
- CVE-2022-36727
- Published
- Aug 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, CAPEC-66, 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
- Error-based bookId SQL injection 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