dbcve.org
Php Gz Appointment Scheduling ScriptApplication · Gzscripts

CVE-2023-3559

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 classified as problematic was found in GZ Scripts PHP GZ Appointment Scheduling Script 1.8. Affected by this vulnerability is an unknown functionality of the file /load.php. The manipulation of the argument first_name/second_name/phone/address_1/country leads to cross site scripting. The attack can be launched remotely. The identifier VDB-233353 was assigned to this vulnerability. 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 reflected cross-site scripting (XSS) vulnerability exists in /load.php of GZ Scripts PHP GZ Appointment Scheduling Script 1.8. The application fails to properly sanitize user input in the first_name, second_name, phone, address_1, and country parameters before reflecting them in the HTML output, allowing injection of malicious JavaScript code.

MitigationImplement input validation and output encoding for all user-supplied parameters in /load.php. Since the vendor did not respond to disclosure, apply third-party patches or manually add proper HTML entity encoding/escaping before reflecting user input in HTTP responses.

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 Appointment Scheduling 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. Identify the installed product
    Locate the PHP GZ Appointment Scheduling Script in the webroot. Check for files like load.php, or look for the application's main directory structure.
    Affected if The GZ Appointment Scheduling Script is installed on the server.
  2. Confirm the product version
    Check the version number in the application source code, typically found in a version file, readme, or the main script header. Common locations include a file named version.php or within the main index/header files.
    Affected if The installed version is exactly 1.8.
  3. Locate the vulnerable endpoint
    Verify that /load.php exists in the web application directory and is accessible via HTTP.
    Affected if The file load.php is present and reachable.
  4. Identify affected parameters in use
    Review the load.php source code to confirm it processes the first_name, second_name, phone, address_1, and country parameters. These are typically form inputs submitted via GET or POST requests.
    Affected if The application accepts and reflects these parameters without sanitization.
  5. Check for lack of output encoding
    Examine the load.php source code for the sections where these parameters are echoed or printed back to the HTML response. Look for direct output of the parameter values without htmlspecialchars() or equivalent encoding.
    Affected if The parameter values are reflected in HTML without proper encoding functions.

You are affected if GZ Appointment Scheduling Script version 1.8 is installed, the load.php file exists, and it reflects any of the first_name, second_name, phone, address_1, or country parameters without HTML entity encoding.

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 input validation and output encoding for all user-supplied parameters in /load.php. Since the vendor did not respond to disclosure, apply third-party patches or manually add proper HTML entity encoding/escaping before reflecting user input in HTTP responses.

Fix this in Php Gz Appointment Scheduling Script 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-3559 — 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-3559 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