dbcve.org
Responsive Hotel SiteApplication · Fabian

CVE-2025-13076

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-12
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 code-projects Responsive Hotel Site 1.0. The affected element is an unknown function of the file /admin/usersetting.php. Executing manipulation of the argument usname can lead to sql injection. The attack can be executed 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 · moderate confidence

SQL injection vulnerability in the usname parameter of /admin/usersetting.php in Responsive Hotel Site 1.0 allows remote attackers to inject malicious SQL queries. The vulnerability stems from unsanitized user input being directly incorporated into SQL statements.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements in usersetting.php. Additionally, implement input validation and output encoding for all user-supplied data.

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
Responsive Hotel SiteApplication
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 if Responsive Hotel Site is installed
    Search the web root directory for files named 'usersetting.php' or check for directories containing 'hotel' or 'responsive' in the name. On Linux: find /var/www -name 'usersetting.php' 2>/dev/null. On Windows: search for usersetting.php in web directories.
    Affected if The application is running and the file /admin/usersetting.php exists in the web root.
  2. Determine the installed version
    Check for version information in the application. Look for version.txt, README files, or meta tags in index pages. Examine the footer of the main page for version numbers. Compare against the affected version: 1.0.
    Affected if The installed version is Fabian Responsive Hotel Site version 1.0.
  3. Verify the vulnerable PHP file exists
    Locate the file /admin/usersetting.php in the web application directory. Check if it contains SQL query logic. Inspect the file for dynamic SQL statements using the usname parameter.
    Affected if The file /admin/usersetting.php exists and processes the usname parameter in SQL queries without sanitization.
  4. Confirm admin interface accessibility
    Check if the /admin/ directory is accessible via HTTP/HTTPS. Verify that usersetting.php can be reached through the web server. Test access to the admin login page.
    Affected if The admin panel is accessible and the usersetting.php endpoint is reachable over the network.
  5. Check for unsanitized parameter handling
    Examine the source code of usersetting.php. Look for SQL queries that directly incorporate the usname parameter without using prepared statements, parameterized queries, or input sanitization functions.
    Affected if The code shows direct insertion of the usname parameter into SQL statements without escaping or prepared statements.

The environment is affected if Responsive Hotel Site version 1.0 is running with the /admin/usersetting.php file accessible and the usname parameter handled in SQL queries without parameterization.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries or prepared statements in usersetting.php. Additionally, implement input validation and output encoding for all user-supplied data.

Fix this in Responsive Hotel Site Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13076 — 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-2025-13076 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