CVE-2026-3746
SQL Injection in SourceCodester Tourism Website Login Component
Publication date: 2026-03-08
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-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': 'CVE-2026-3746 is a critical SQL injection vulnerability found in SourceCodester Simple Responsive Tourism Website version 1.0, specifically in the Login component located at /tourism/classes/Login.php with the parameter "username" in the login function. The vulnerability arises because the application constructs SQL commands using externally influenced input from the "username" parameter without properly neutralizing special characters, leading to improper neutralization of special elements used in an SQL command (CWE-89).'}, {'type': 'paragraph', 'content': 'This flaw allows remote attackers to execute arbitrary SQL commands without requiring any authentication, making it possible to manipulate the database through SQL injection techniques.'}] [1]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, data leakage, data manipulation, and full system control by attackers. It can also lead to service disruption.
- Attackers can execute arbitrary SQL commands remotely without authentication.
- Confidentiality, integrity, and availability of the system can be compromised.
- Potential exposure and unauthorized modification or deletion of sensitive data.
- Attackers may gain full control over the affected system.
- Service disruption or denial of service may occur.
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 login functionality of the affected application, specifically targeting the 'username' parameter in the /tourism/classes/Login.php?f=login endpoint for SQL injection flaws."}, {'type': 'paragraph', 'content': 'Common detection methods include using SQL injection payloads such as Boolean-based blind, error-based, and time-based blind SQL injection techniques.'}, {'type': 'list_item', 'content': "Boolean-based blind SQL injection payload example: username=admin' AND 7827=7827 AND 'JpDZ'='JpDZ"}, {'type': 'list_item', 'content': "Error-based SQL injection payload example for MySQL 5.0+: username=admin' AND (SELECT 2960 FROM(SELECT COUNT(*),CONCAT(0x7170716b71,(SELECT (ELT(2960=2960,1))),0x716a767871,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)"}, {'type': 'list_item', 'content': "Time-based blind SQL injection payload example for MySQL >= 5.0.12: username=admin' OR (SELECT 8515 FROM (SELECT(SLEEP(5)))KHUI)"}, {'type': 'paragraph', 'content': 'Automated tools like sqlmap can be used to confirm the presence of the vulnerability and enumerate the database.'}] [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected product with an alternative solution, as no official patch or fix has been provided by the vendor.
Implement prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection.
Apply strict input validation and filtering to ensure inputs conform to expected formats.
Minimize database user permissions by avoiding the use of high-privilege accounts (such as root or admin) for routine database operations.
Conduct regular security audits to detect and remediate vulnerabilities promptly.