dbcve.org
Availability Booking Calendar PhpApplication · Gzscripts

CVE-2023-3543

MEDIUM · 6.1 CVSS v3.1 Published 2023-07-07
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 was found in GZ Scripts Availability Booking Calendar PHP 1.8. It has been classified as problematic. This affects an unknown part of the file load.php of the component HTTP POST Request Handler. The manipulation of the argument cid/first_name/second_name/address_1/country leads to cross site scripting. It is possible to initiate the attack remotely. The associated identifier of this vulnerability is VDB-233295. 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 · moderate confidence

A stored cross-site scripting (XSS) vulnerability exists in GZ Scripts Availability Booking Calendar PHP 1.8. The vulnerability is in the HTTP POST Request Handler of load.php, where the parameters cid, first_name, second_name, address_1, and country are not properly sanitized before being stored and displayed. An attacker can inject malicious JavaScript code through these fields, which will execute when viewed by other users (likely admin staff reviewing bookings).

MitigationImplement server-side input validation and output encoding for all user-supplied parameters. Use context-appropriate output encoding (e.g., htmlspecialchars() for HTML context) when rendering these fields, and validate input against expected formats before storage.

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
Availability Booking Calendar PhpApplication
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 product and version installation
    Locate the GZ Scripts Availability Booking Calendar PHP installation and identify the version number, typically found in a version file, readme, or within the application source code headers
    Affected if The installed version is exactly 1.8 (the only affected version listed)
  2. Locate the vulnerable load.php file
    Find the load.php file within the application directory structure - this is the HTTP POST Request Handler where the vulnerability exists
    Affected if load.php exists and processes booking form submissions containing the fields cid, first_name, second_name, address_1, and country
  3. Inspect POST parameter handling in load.php
    Open load.php and examine how the parameters cid, first_name, second_name, address_1, and country are processed - look for whether these POST inputs are assigned to variables without sanitization
    Affected if These parameters are directly assigned from $_POST without any input validation or sanitization functions (such as htmlspecialchars, strip_tags, or custom validation)
  4. Check for output encoding before storage or display
    Review load.php and any related display/template files to see if these five parameters are encoded with htmlspecialchars() or equivalent before being stored in the database or rendered in HTML
    Affected if The parameters are stored or displayed without HTML entity encoding - no htmlspecialchars() or similar function wraps these values
  5. Verify if the application accepts and processes these user-supplied fields
    Submit a test booking request via HTTP POST to the application endpoint (typically the same page handling bookings) with the fields cid, first_name, second_name, address_1, and country, then view the booking in the admin interface
    Affected if The application accepts and redisplay these fields without sanitization, allowing injected script tags to persist and execute

A defender is affected if they are running GZ Scripts Availability Booking Calendar PHP version 1.8 with load.php handling the listed POST parameters without server-side input validation or output encoding on those fields.

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 server-side input validation and output encoding for all user-supplied parameters. Use context-appropriate output encoding (e.g., htmlspecialchars() for HTML context) when rendering these fields, and validate input against expected formats before storage.

Fix this in Availability Booking Calendar Php 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-2023-3543 — 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-3543 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