CVE-2026-105175 in Drug Recommendation System
Summary
by MITRE • 10/05/2026
A vulnerability was found in SourceCodester Drug Recommendation System 1.0. This issue affects some unknown processing of the file /Auth/add_student.php of the component Student Registration. The manipulation of the argument cmdschool results in sql injection. The attack can be executed remotely. The exploit has been made public and could be used.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 10/05/2026
The SourceCodester Drug Recommendation System version 1.0 contains a critical security flaw within its student registration module, specifically located in the file Auth/add_student.php. This vulnerability manifests as an SQL injection weakness resulting from improper handling of user-supplied input associated with the cmdschool argument. The application fails to adequately sanitize or parameterize this specific variable before incorporating it into database queries. Consequently, an attacker can inject malicious SQL commands that are executed by the backend database server, bypassing intended access controls and data validation logic. This type of flaw is a classic example of CWE-89 Improper Neutralization of Special Elements used in an SQL Command commonly known as SQL Injection which remains one of the most prevalent and dangerous web application vulnerabilities according to OWASP Top 10 standards.
The operational impact of this vulnerability is severe due to its remote exploitability. Since the attack vector does not require local access or physical proximity, a malicious actor can initiate exploitation over a network connection from any location with internet connectivity. The ability to execute arbitrary SQL commands allows for unauthorized data extraction which may include sensitive student records personal identifiable information and potentially administrative credentials stored within the database. Furthermore depending on the underlying database configuration privileges an attacker might escalate their access to perform destructive actions such as modifying or deleting critical application data disrupting service availability or even gaining control over the host operating system through out-of-band execution techniques if supported by the specific SQL engine in use.
The fact that a public exploit exists significantly lowers the barrier for entry allowing less sophisticated threat actors to leverage this vulnerability against targeted systems. This increases the likelihood of automated scanning and opportunistic attacks across vulnerable instances deployed on the internet. Organizations relying on this open-source system must recognize that without immediate remediation their data integrity confidentiality and availability are at significant risk. The presence of a public exploit also means that defensive measures such as basic web application firewalls may be bypassed if they do not specifically detect the patterns associated with this particular injection vector in the cmdschool parameter.
Mitigation strategies should focus on both immediate patching and long-term architectural improvements. Developers must implement strict input validation ensuring that all data entering from external sources is checked against expected formats types and lengths before processing. More importantly prepared statements or parameterized queries should be utilized for all database interactions to ensure that user input is treated strictly as data rather than executable code thereby neutralizing the injection attempt regardless of its content. Additionally implementing a Web Application Firewall with rules tuned to detect SQL injection patterns can provide an additional layer of defense while patches are being developed and deployed. Regular security audits and static application security testing should be integrated into the development lifecycle to prevent similar flaws from recurring in future versions or related components of the system aligning with secure coding practices recommended by industry standards such as CWE-89 and MITRE ATT&CK techniques associated with data exfiltration via SQL injection like T1059.