Unauthenticated SQL injection via unsanitized username parameter
Published Sep 18, 2025 · Updated Sep 18, 2025
SQL injection in SourceCodester Responsive E-Learning System 1.0 allows remote attackers to manipulate database queries via add_teacher.php. The handler inserts the multipart username parameter directly into a SQL query without validation or parameter binding, enabling time-based blind payloads. No login or authorization is required, and successful exploitation permits unauthorized database reads and writes.
Summary
What happened
SQL injection in SourceCodester Responsive E-Learning System 1.0 allows remote attackers to manipulate database queries via add_teacher.php. The handler inserts the multipart username parameter directly into a SQL query without validation or parameter binding, enabling time-based blind payloads. No login or authorization is required, and successful exploitation permits unauthorized database reads and writes.
The record
- CVE
- CVE-2025-10687
- Published
- Sep 18, 2025
- Updated
- Sep 18, 2025
- Vendor
- Online Computer and Laptop Store Project
- Product
- Responsive E-Learning System
- Classifications
- CWE-89, CWE-74, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2025CVE publishedPublication date reported by the CVE source.
- Sep 18, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0
What conditions does exploitation require?
What is affected?
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
- Time-based blind username 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