dbcve.org
Simple Responsive Tourism WebsiteApplication · Oretnom23

CVE-2026-2848

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A flaw has been found in SourceCodester Simple Responsive Tourism Website 1.0. Affected by this vulnerability is an unknown functionality of the file /classes/Master.php?f=register of the component Registration. This manipulation of the argument Username causes sql injection. The attack may be initiated remotely. The exploit has been published and may be used.

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 · high confidence

A critical SQL injection vulnerability exists in SourceCodester Simple Responsive Tourism Website 1.0 within the registration handler at /classes/Master.php?f=register. The Username parameter passed to the register function is not properly sanitized, allowing attackers to inject arbitrary SQL commands. This can lead to complete database compromise, including unauthorized access, data exfiltration, or privilege escalation.

MitigationImplement prepared statements/parameterized queries for all database operations in the registration function, particularly for the Username field. Apply input validation and escaping as an additional defense layer.

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
Simple Responsive Tourism WebsiteApplication
Affected:= 1.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed application
    Check if the website is built with SourceCodester Simple Responsive Tourism Website by looking for the application's file structure, typically found in the web root directory. Look for characteristic files or headers that identify this specific application.
    Affected if The application is SourceCodester Simple Responsive Tourism Website and the version is 1.0
  2. Verify the version number
    Locate the version information in the application. This may be in a README file, a version config file, or the source code headers. Compare the installed version against the affected version 1.0.
    Affected if The installed version is exactly 1.0
  3. Confirm the vulnerable endpoint exists
    Verify that the file /classes/Master.php exists in the web application directory and that it contains a 'register' function handler. This file is typically found in the classes subdirectory of the application root.
    Affected if The file /classes/Master.php exists and contains a register function handler at the expected path
  4. Inspect the registration code for SQL injection vulnerability
    Open /classes/Master.php and locate the register function. Examine how the Username parameter is handled - look for direct string concatenation or unsanitized use of the username in SQL queries instead of parameterized queries.
    Affected if The Username parameter from the registration form is used directly in SQL queries without proper sanitization or prepared statements
  5. Check if registration functionality is enabled
    Verify that the registration endpoint is accessible and functional. Attempt to access the registration page or send a registration request to confirm the feature is active. Check configuration files for any registration enable/disable flags.
    Affected if The registration functionality is enabled and accessible, allowing external users to submit requests to /classes/Master.php?f=register

A user is affected if they have SourceCodester Simple Responsive Tourism Website version 1.0 installed with the registration endpoint at /classes/Master.php?f=register exposed and the Username parameter handled without parameterized queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all database operations in the registration function, particularly for the Username field. Apply input validation and escaping as an additional defense layer.

Recommended fix High confidence
  1. This is a SourceCodester open-source project with no vendor-provided security patches or fixed versions available.
  2. Review the vulnerable code in /classes/Master.php around the register function to identify the SQL injection point.
  3. Implement parameterized queries/prepared statements for all database operations in the registration logic.
  4. Apply proper input validation and sanitization for the Username parameter and all user inputs.
  5. Consider deploying a Web Application Firewall (WAF) as an additional layer of protection.
  6. If available, check the GitHub repository for community forks that may have addressed the vulnerability.
  7. If the project is no longer maintained, consider migrating to a supported tourism website solution with active security updates.
Caveat No official upgrade path exists for this project; this is an end-of-life/unmaintained SourceCodester project

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Simple Responsive Tourism Website Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2848 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2848 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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