CVE-2026-4625
SQL Injection in SourceCodester Online Admission System /programmes.php
Publication date: 2026-03-24
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sourcecodester | online_admission_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-4625 is a critical SQL injection vulnerability found in version 1.0 of the SourceCodester Online Admission System, specifically in the /programmes.php file.'}, {'type': 'paragraph', 'content': "The vulnerability occurs because the 'program' parameter is improperly handled and directly incorporated into SQL queries without adequate input validation or sanitization."}, {'type': 'paragraph', 'content': 'This flaw allows attackers to inject malicious SQL code remotely, without requiring authentication.'}, {'type': 'paragraph', 'content': 'Attackers can exploit this to gain unauthorized access to the database, leak or manipulate data, compromise the entire system, and potentially disrupt services.'}, {'type': 'paragraph', 'content': 'Multiple SQL injection techniques can be used, including boolean-based blind, error-based, time-based blind, and UNION query injections.'}] [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to view sensitive information.
Attackers may manipulate or delete data, causing data integrity issues.
Full system compromise is possible, which can lead to further attacks or control over the affected system.
Service disruption may occur, impacting availability and reliability of the online admission system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This SQL injection vulnerability in the /programmes.php file can be detected by testing the 'program' GET parameter for injection flaws using various SQL injection techniques."}, {'type': 'list_item', 'content': 'Boolean-based blind test payload: program=1 AND 6471=6471'}, {'type': 'list_item', 'content': 'Error-based test payload (MySQL ≥ 5.6): program=1 AND GTID_SUBSET(CONCAT(0x7170717071,(SELECT (ELT(1315=1315,1))),0x716a7a7171),1315)'}, {'type': 'list_item', 'content': 'Time-based blind test payload (MySQL ≥ 5.0.12): program=1 AND (SELECT 3271 FROM (SELECT(SLEEP(5)))HZHZ)'}, {'type': 'list_item', 'content': 'UNION query injection with 9 columns: program=-5411 UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,CONCAT(0x7170717071,0x4d676e7046637a42775468656349725052744a48666f45575478656a47426e6d584459705a4e7649,0x716a7a7171)-- -'}, {'type': 'paragraph', 'content': 'Additionally, automated tools like sqlmap can be used to detect this vulnerability with parameters --batch --level 5 --risk 2.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this SQL injection vulnerability, immediate steps include:
- Use prepared statements with parameter binding to separate SQL code from user input, preventing injection.
- Implement strict input validation and filtering to ensure inputs conform to expected formats.
- Minimize database user permissions by avoiding use of high-privilege accounts (such as root or admin) for routine database operations.
- Conduct regular security audits of code and systems to detect and address vulnerabilities promptly.