dbcve.org
Php Gz Hotel Booking ScriptApplication · Gzscripts

CVE-2023-3561

MEDIUM · 6.1 CVSS v3.1 Published 2023-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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, which was classified as problematic, was found in GZ Scripts PHP GZ Hotel Booking Script 1.8. This affects an unknown part of the file /load.php. The manipulation of the argument first_name/second_name/phone/address_1/country leads to cross site scripting. It is possible to initiate the attack remotely. The associated identifier of this vulnerability is VDB-233355. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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 stored Cross-Site Scripting (XSS) vulnerability exists in GZ Scripts PHP GZ Hotel Booking Script 1.8 within the /load.php file. User-supplied input to the first_name, second_name, phone, address_1, and country parameters is not properly sanitized before storage or rendering, allowing injection of arbitrary JavaScript. This is a medium-severity (CVSS 6.1) issue exploitable remotely.

MitigationImplement proper input validation and output encoding/escaping for all user-supplied parameters in load.php. Use context-appropriate sanitization (e.g., htmlspecialchars for HTML contexts) and consider Content Security Policy headers 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
Php Gz Hotel Booking ScriptApplication
Affected:= 1.8

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 the GZ Hotel Booking Script version
    Locate and inspect the version file, admin panel, or footer of the application to verify the installed version is 1.8
    Affected if The installed version is exactly 1.8 (the only affected version listed)
  2. Locate the load.php file
    Search the web root directory for the file /load.php or check common paths such as /admin/load.php or the application root
    Affected if The file load.php exists in the application installation
  3. Inspect code handling first_name and second_name parameters
    Open load.php and search for code handling the 'first_name' and 'second_name' POST/GET parameters to see if they are stored in the database and later rendered without sanitization (e.g., missing htmlspecialchars)
    Affected if The parameters are processed and stored without proper sanitization functions like htmlspecialchars or equivalent encoding
  4. Inspect code handling phone, address_1, and country parameters
    Search load.php for handling of 'phone', 'address_1', and 'country' parameters and verify if output encoding is applied when these values are rendered back to the user
    Affected if These parameters are stored and rendered without sanitization
  5. Identify if user registration or profile editing is accessible
    Determine if the application allows unauthenticated or low-privilege users to access the forms that submit data to load.php (typically registration or booking forms)
    Affected if Users can submit data to the affected parameters without admin-level access controls

A user is affected if they have GZ Hotel Booking Script version 1.8 installed with the load.php file present and accessible, where user input for first_name, second_name, phone, address_1, or country is stored and displayed without sanitization.

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 proper input validation and output encoding/escaping for all user-supplied parameters in load.php. Use context-appropriate sanitization (e.g., htmlspecialchars for HTML contexts) and consider Content Security Policy headers as defense-in-depth.

Fix this in Php Gz Hotel Booking Script Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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