CVE-2026-2848
SQL Injection in SourceCodester Tourism Website Registration Module
Publication date: 2026-02-20
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 |
|---|---|---|
| oretnom23 | simple_responsive_tourism_website | 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?
CVE-2026-2848 is a critical SQL injection vulnerability found in SourceCodester Simple Responsive Tourism Website version 1.0. The flaw exists in the file `/classes/Master.php` within the Registration component, specifically when handling the `username` parameter during the registration process (`f=register`).
Improper sanitization or neutralization of this externally supplied input allows an attacker to manipulate SQL commands, leading to SQL injection (CWE-89). This means an attacker can inject malicious SQL code into the database query, potentially compromising the system.
The attack can be launched remotely without any authentication, making exploitation straightforward and accessible. Proof-of-concept exploits demonstrate multiple SQL injection techniques such as Boolean-based blind, error-based, and time-based blind SQL injection.
How can this vulnerability impact me? :
Exploiting this vulnerability enables unauthorized database access, allowing attackers to retrieve sensitive information, modify or delete data, and potentially disrupt the availability of the system.
The vulnerability impacts the confidentiality, integrity, and availability of the affected system, potentially leading to full system compromise or service disruption.
- Unauthorized data leakage
- Data manipulation or deletion
- Potential full system compromise
- Service disruption or denial of service
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This SQL injection vulnerability can be detected by testing the 'username' parameter in the registration function for injection flaws."}, {'type': 'paragraph', 'content': 'Common detection methods include using SQL injection testing tools such as sqlmap to send crafted payloads to the vulnerable parameter and observe the responses.'}, {'type': 'list_item', 'content': "Boolean-based blind SQL injection payload example: username=1' AND 2418=2418 AND 'OEKt'='OEKt"}, {'type': 'list_item', 'content': "Error-based SQL injection payload example for MySQL ≥ 5.6: username=1' AND GTID_SUBSET(CONCAT(0x7170717171,(SELECT (ELT(4334=4334,1))),0x7162717871),4334) AND 'tGjS'='tGjS"}, {'type': 'list_item', 'content': "Time-based blind SQL injection payload example for MySQL ≥ 5.0.12: username=1' AND (SELECT 3300 FROM (SELECT(SLEEP(5)))RJoR) AND 'LsRB'='LsRB"}, {'type': 'paragraph', 'content': "Using sqlmap with the target URL and specifying the 'username' parameter can automate detection and enumeration of the vulnerability."}] [3]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include replacing the affected product with an alternative solution if possible.'}, {'type': 'paragraph', 'content': 'If replacement is not feasible, implement prepared statements with parameter binding to separate SQL code from user input, preventing injection.'}, {'type': 'paragraph', 'content': "Enforce strict input validation and filtering on the 'username' parameter to ensure it conforms to expected formats."}, {'type': 'paragraph', 'content': "Minimize database user privileges by avoiding the use of high-privilege accounts (such as root or admin) for the application's database connections."}, {'type': 'paragraph', 'content': 'Conduct regular security audits of the code and systems to detect and fix vulnerabilities promptly.'}] [1, 3, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know