CVE-2023-6075
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 classified as problematic has been found in PHPGurukul Restaurant Table Booking System 1.0. Affected is an unknown function of the file index.php of the component Reservation Request Handler. The manipulation leads to cross site scripting. It is possible to launch the attack remotely. The identifier of this vulnerability is VDB-244944.
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 the Reservation Request Handler of index.php in PHPGurukul Restaurant Table Booking System 1.0. The application fails to properly sanitize user input when processing reservation requests, allowing malicious scripts to be injected and executed in the browsers of other users who view the reservation data.
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.0CVSS 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 PHPGurukul Restaurant Table Booking System is presentLocate the application files on the web server. Look for index.php and other PHP files related to restaurant table booking. Check the web server document root for the application installation.Affected if The PHPGurukul Restaurant Table Booking System is installed on the server
-
Verify the exact application versionExamine the source code for version information, typically found in a version file, README, or in comments within index.php. The vulnerability specifically affects version 1.0.Affected if The installed version is exactly 1.0
-
Locate the Reservation Request Handler in index.phpOpen index.php and search for code handling reservation submissions. Look for form processing logic that accepts user input for table booking requests.Affected if index.php contains the Reservation Request Handler functionality
-
Inspect input sanitization in reservation handling codeReview the reservation processing code for proper input validation. Check if user-supplied fields (such as name, contact, date, time, number of guests) are sanitized before being stored or displayed. Look for missing htmlspecialchars, strip_tags, or other encoding functions.Affected if User input in reservation fields is not sanitized or encoded before storage or output
-
Test for stored XSS in reservation submissionSubmit a reservation request with a test script payload in available input fields (e.g., name field: <script>alert(1)</script>). Then access the reservation list or admin panel where booking data is displayed to see if the script executes.Affected if Malicious script tags submitted in reservation input fields are rendered unescaped when viewed by other users
The environment is affected if PHPGurukul Restaurant Table Booking System version 1.0 is installed and the Reservation Request Handler in index.php fails to sanitize user input, allowing stored XSS to execute when reservation data is viewed.
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 context-aware output encoding for all user-supplied data in the reservation handler. Additionally, implement Content Security Policy (CSP) headers to provide defense-in-depth against XSS attacks.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6075 — 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-6075 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