CVE-2026-4573
SQL Injection in SourceCodester E-learning delete_post.php
Publication date: 2026-03-23
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 | simple_e-learning_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'The CVE-2026-4573 vulnerability is a Time-based Blind SQL Injection found in the Simple E-learning System version 1.0, specifically within the Delete Post functionality located at `/includes/form_handlers/delete_post.php`.'}, {'type': 'paragraph', 'content': 'The vulnerability arises because the application does not properly sanitize the `post_id` parameter received via a GET request before incorporating it into a SQL query.'}, {'type': 'paragraph', 'content': "This flaw allows an authenticated attacker to inject malicious SQL commands. The attack exploits the server's response time by using SQL commands such as `SLEEP()`, enabling the attacker to infer database information one byte at a time without direct output, effectively performing data exfiltration."}, {'type': 'paragraph', 'content': 'The backend database is MySQL version 5.0.12 or higher, and the web application runs on PHP 7.4.33 with Apache 2.4.54.'}] [1]
How can this vulnerability impact me? :
This vulnerability can be exploited by an authenticated attacker to perform unauthorized data exfiltration.
- Retrieving sensitive information such as usernames and password hashes.
- Full database enumeration including tables and columns.
The attacker achieves this by exploiting the unsanitized `post_id` parameter to inject SQL commands that manipulate the database and extract data.
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 vulnerability can be detected by testing the `post_id` parameter in the URL `/includes/form_handlers/delete_post.php` for SQL injection using time-based blind SQL injection techniques.'}, {'type': 'paragraph', 'content': 'A common approach is to intercept a delete post request with a proxy tool like Burp Suite and then use sqlmap to test the parameter.'}, {'type': 'paragraph', 'content': 'An example sqlmap command to detect the vulnerability is:'}, {'type': 'list_item', 'content': 'sqlmap -u "http://127.0.0.1:8081/includes/form_handlers/delete_post.php?post_id=3&classCode=class101_a" --batch -v 6 --risk=3 --cookie "PHPSESSID=YOUR_COOKIE_HERE"'}, {'type': 'paragraph', 'content': 'This command uses sqlmap to send requests with the `post_id` parameter and detect time delays caused by the SQL `SLEEP()` function, confirming the presence of the SQL injection.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
I don't know