dbcve.org
Responsive Hotel SiteApplication · Fabian

CVE-2025-12857

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-07
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 security vulnerability has been detected in code-projects Responsive Hotel Site 1.0. The affected element is an unknown function of the file /admin/roombook.php. Such manipulation of the argument rid leads to sql injection. The attack can be launched remotely. The exploit has been disclosed publicly 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

SQL injection vulnerability in code-projects Responsive Hotel Site 1.0 allows remote attackers to inject malicious SQL queries via the 'rid' parameter in /admin/roombook.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially leading to unauthorized data access, modification, or complete system compromise.

MitigationImplement prepared statements/parameterized queries for all database operations in roombook.php, particularly for the 'rid' parameter. Apply input validation and escape special characters. Consider implementing a Web Application Firewall as defense-in-depth.

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. Confirm Responsive Hotel Site installation
    Locate the web root directory and look for files named 'roombook.php' or directories containing 'hotel' or 'responsive' in the path. Check for typical installation paths like /var/www/html/, /www/, or C:\inetpub\wwwroot\.
    Affected if The application files (particularly /admin/roombook.php) are present on the server.
  2. Verify the product version
    Inspect the source code for a version identifier. Check files like README, version.php, or the main index.php for a version number '1.0'. Look for banner strings or metadata comments in PHP files.
    Affected if The installed version is exactly 1.0 (Responsive Hotel Site).
  3. Locate the vulnerable file
    Search for the file /admin/roombook.php in the web application directory structure. This file handles room booking operations and contains the vulnerable 'rid' parameter handling.
    Affected if The file /admin/roombook.php exists and is accessible via the web server.
  4. Check if the admin panel is accessible
    Attempt to access the /admin/ directory or /admin/roombook.php endpoint via HTTP/HTTPS. Verify whether authentication is required or if the endpoint is directly accessible.
    Affected if The /admin/roombook.php endpoint is reachable without requiring authentication or with weak authentication.
  5. Inspect the 'rid' parameter handling
    Review the source code of roombook.php. Look for SQL queries that directly incorporate the 'rid' parameter without using prepared statements, parameterized queries, or input sanitization functions like mysqli_prepare or PDO::prepare.
    Affected if The code contains SQL queries that concatenate or interpolate the 'rid' parameter directly into the query string without sanitization.

A user is affected if they are running Responsive Hotel Site version 1.0 with the /admin/roombook.php file accessible and the 'rid' parameter handled in SQL queries 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.

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

Implement prepared statements/parameterized queries for all database operations in roombook.php, particularly for the 'rid' parameter. Apply input validation and escape special characters. Consider implementing a Web Application Firewall as defense-in-depth.

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-12857 — 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-12857 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