CVE-2026-3746
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was determined in SourceCodester Simple Responsive Tourism Website 1.0. Affected by this vulnerability is an unknown functionality of the file /tourism/classes/Login.php?f=login of the component Login. This manipulation of the argument Username causes sql injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in the login functionality of SourceCodester Simple Responsive Tourism Website 1.0. The Username parameter in /tourism/classes/Login.php?f=login is not properly sanitized, allowing attackers to inject malicious SQL queries and potentially bypass authentication, extract data, or compromise the database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm the application is installedLocate the SourceCodester Simple Responsive Tourism Website by searching for the 'tourism' directory structure on your web server. Common paths include /var/www/html/tourism/ or C:\inetpub\wwwroot\tourism\Affected if The tourism directory with the Simple Responsive Tourism Website exists on the server
-
Verify the product version is 1.0Check for version indicators such as a version.php file, README file, or any documentation within the tourism directory that states the version numberAffected if The installed version is exactly 1.0 as indicated by version files or documentation
-
Confirm the vulnerable login file existsVerify the existence of /tourism/classes/Login.php in your web directory. This is the file containing the vulnerable login functionality at the '?f=login' endpointAffected if The file /tourism/classes/Login.php exists and is accessible via web requests
-
Check if the login function uses unsanitized inputExamine the Login.php file source code and locate the login function. Look for direct use of the username parameter in SQL queries without parameterized queries or proper escaping (e.g., $username directly concatenated into SELECT statements)Affected if The login code contains SQL queries where the username parameter is inserted directly without prepared statements, binding parameters, or escaping functions
-
Confirm the login endpoint is accessibleTest accessing the login functionality by making a request to the login form page or directly to the ?f=login endpoint to confirm the application is actively runningAffected if The login functionality is active and accessible on the web server
You are affected if the Simple Responsive Tourism Website version 1.0 is installed with the Login.php file present and the login code contains unsanitized SQL query construction using the username parameter.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement parameterized queries (prepared statements) for all database operations in the login function to prevent SQL injection. Additionally, apply input validation on the Username field and ensure the database user has minimal required privileges.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3746 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data