Authentication bypass via student login SQL injection
Published Feb 15, 2021 · Updated Aug 3, 2024
SQL injection in Library System 1.0 allows remote attackers to bypass authentication and access the privileged student area. The login.php handler places the student POST value into its authentication query, allowing an always-true OR expression to satisfy the lookup. No account is required, but the published exploit establishes privileged student-area access rather than broader database or host control.
Summary
What happened
SQL injection in Library System 1.0 allows remote attackers to bypass authentication and access the privileged student area. The login.php handler places the student POST value into its authentication query, allowing an always-true OR expression to satisfy the lookup. No account is required, but the published exploit establishes privileged student-area access rather than broader database or host control.
The record
- CVE
- CVE-2021-26200
- Published
- Feb 15, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 15, 2021CVE 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
- Library System 1.0 Authentication Bypass exploitfunctional · 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