dbcve.org
Responsive Hotel SiteApplication · Fabian

CVE-2023-1498

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-19
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
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 vulnerability classified as critical has been found in code-projects Responsive Hotel Site 1.0. Affected is an unknown function of the file messages.php of the component Newsletter Log Handler. The manipulation of the argument title leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-223398 is the identifier assigned to this vulnerability.

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 the Newsletter Log Handler component of the Responsive Hotel Site 1.0 application (messages.php). The 'title' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL commands. This can lead to unauthorized database access, data exfiltration, or potential system compromise.

MitigationImmediately patch the vulnerable messages.php file by replacing dynamic SQL queries with parameterized queries/prepared statements. Alternatively, implement input validation and escaping for the 'title' parameter until a proper fix can be applied. Restrict network access to the affected endpoint as an interim control.

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. Locate the Responsive Hotel Site installation
    Search the web server filesystem for files belonging to the Responsive Hotel Site application, typically under the web root directory (e.g., /var/www/html, /htdocs, or C:\inetpub\wwwroot). Look for common hotel site directories or check server configuration for hosted applications.
    Affected if The application files are present on the server.
  2. Verify the application version
    Check for a version file, readme, or any version identifier within the application root directory. Compare the installed version to the affected version: Responsive Hotel Site 1.0.
    Affected if The installed version is exactly 1.0.
  3. Identify the vulnerable messages.php file
    Locate the messages.php file within the application directory structure. This file contains the Newsletter Log Handler component where the SQL injection exists.
    Affected if The messages.php file exists in the application installation.
  4. Confirm the 'title' parameter is accessible
    Examine the messages.php source code to verify it accepts user input through the 'title' parameter via GET or POST requests. This confirms the attack surface exists.
    Affected if The 'title' parameter is used in the messages.php script without sanitization.
  5. Check for indicators of exploitation
    Review web server access logs and application logs for suspicious SQL patterns in requests to messages.php, such as UNION SELECT, OR 1=1, or other SQL injection payloads targeting the title parameter.
    Affected if Malicious SQL injection attempts appear in logs targeting the title parameter.

You are affected if the Responsive Hotel Site version 1.0 is installed and the messages.php file with the vulnerable 'title' parameter is accessible on your server.

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

Immediately patch the vulnerable messages.php file by replacing dynamic SQL queries with parameterized queries/prepared statements. Alternatively, implement input validation and escaping for the 'title' parameter until a proper fix can be applied. Restrict network access to the affected endpoint as an interim control.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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