CVE-2023-6076
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 was found in PHPGurukul Restaurant Table Booking System 1.0. Affected by this vulnerability is an unknown functionality of the file booking-details.php of the component Reservation Status Handler. The manipulation of the argument bid leads to information disclosure. The attack can be launched remotely. The identifier VDB-244945 was assigned to this vulnerability.
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 confidenceIDOR vulnerability in PHPGurukul Restaurant Table Booking System 1.0 where the booking-id parameter (bid) in booking-details.php can be manipulated to view reservations belonging to other users, exposing sensitive reservation information without proper authorization checks.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installedLocate the installation directory (often in web root, /var/www/html or similar). Look for files like index.php, header.php, or config files that identify this specific product. Check for version identifier '1.0' in any version file or documentation.Affected if The application directory contains PHPGurukul Restaurant Table Booking System files, specifically version 1.0
-
Locate the booking-details.php fileSearch the web root for the file booking-details.php. Common paths may include /booking-details.php or within a /booking/ subdirectory.Affected if The file booking-details.php exists in the web application directory
-
Check if bid parameter is processed without authorizationOpen booking-details.php in a text editor. Search for code that retrieves the 'bid' parameter (e.g., $_GET['bid'] or $_POST['bid']) and directly queries the database without checking if the logged-in user owns that booking.Affected if The code takes the bid parameter and runs a database query to fetch booking details without validating that the current user has permission to view that specific booking
-
Test for IDOR vulnerabilityLog in as a regular user with a booking. Note the booking ID (bid) in the URL or form. Log out and access booking-details.php?bid=[another_users_booking_id] or log in as a different user and try to access another user's booking ID. If the reservation details display without an authorization error, the vulnerability is present.Affected if Requesting booking-details.php with a bid value belonging to a different user returns that user's reservation data without requiring ownership verification
You are affected if PHPGurukul Restaurant Table Booking System version 1.0 is installed and booking-details.php allows viewing any booking by manipulating the bid parameter without verifying user ownership.
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 authorization checks in booking-details.php to verify the authenticated user has rights to view the requested booking before returning any data. Consider adding session-based ownership validation for all reservation lookups.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6076 — 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-6076 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