CVE-2023-3544
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 · uneditedA vulnerability was found in GZ Scripts Time Slot Booking Calendar PHP 1.8. It has been declared as problematic. This vulnerability affects unknown code 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 initiated remotely. The identifier of this vulnerability is VDB-233296. 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 confidenceA stored cross-site scripting (XSS) vulnerability exists in GZ Scripts Time Slot Booking Calendar PHP 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 and display, allowing injection of malicious JavaScript code.
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= 1.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm installed product versionLocate the GZ Scripts Time Slot Booking Calendar PHP installation directory and check the version. Look for a version file, about page, or check the header/comment blocks in load.php for a version string. Compare against the affected version 1.8.Affected if The installed version is exactly 1.8 of GZ Scripts Time Slot Booking Calendar PHP.
-
Locate vulnerable load.php fileNavigate to the web root of the Time Slot Booking Calendar installation and verify that /load.php exists. This is the file containing the vulnerable code.Affected if The file /load.php exists in the booking calendar installation directory.
-
Verify booking form is accessibleAccess the booking calendar frontend where users submit their details. Confirm that forms accept input for first_name, second_name, phone, address_1, and country parameters.Affected if The booking form accepts and stores user input for the named parameters.
-
Inspect stored data for XSS payloadsExamine the backend database or admin panel where booking records are stored. Look for any stored entries containing HTML, JavaScript tags, or script-related characters in the name, phone, address, or country fields.Affected if Any records in the database contain unescaped HTML or JavaScript code in the first_name, second_name, phone, address_1, or country fields.
You are affected if the installed version is exactly 1.8 and the application stores user-submitted data from the first_name, second_name, phone, address_1, or country parameters without sanitization.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper input validation and output encoding/escaping for all user-supplied parameters (first_name, second_name, phone, address_1, country) in load.php to prevent XSS execution.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3544 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-3544 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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