CVE-2023-6767
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, which was classified as problematic, was found in SourceCodester Wedding Guest e-Book 1.0. This affects an unknown part of the file /endpoint/add-guest.php. The manipulation of the argument name leads to cross site scripting. It is possible to initiate the attack remotely. The associated identifier of this vulnerability is VDB-247899.
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 cross-site scripting (XSS) vulnerability exists in the Wedding Guest e-Book 1.0 application at the /endpoint/add-guest.php endpoint. The 'name' parameter is not properly sanitized, allowing an attacker to inject malicious JavaScript code that executes in the context of other users' browsers.
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.
-
Locate the Wedding Guest e-Book installationSearch the web root for directories containing 'wedding', 'guest', or 'ebook' in the name, or check common web server directories (htdocs, www, public_html) for the application files.Affected if The application is present on the server
-
Verify the application versionLook for a version file, readme.txt, or any file within the application that displays the version number. Compare against the affected version 1.0.Affected if The installed version is exactly 1.0
-
Confirm the vulnerable endpoint existsCheck for the presence of the file /endpoint/add-guest.php within the application directory structure.Affected if The file /endpoint/add-guest.php exists and is accessible via the web server
-
Inspect the add-guest.php source codeOpen /endpoint/add-guest.php and examine how the 'name' parameter is handled. Look for whether htmlspecialchars, ENT_QUOTES, or any sanitization function is applied before the parameter is used in output or stored.Affected if The 'name' parameter is processed without proper sanitization (no htmlspecialchars, ENT_QUOTES, or equivalent encoding before output)
-
Test for reflected input (if endpoint is live)Submit a test request to /endpoint/add-guest.php with a harmless test string in the 'name' parameter (e.g., <script>alert('test')</script>), then check if that string is reflected back in the response without encoding.Affected if The submitted 'name' value is reflected in the response without HTML encoding
A user is affected if the Wedding Guest e-Book version 1.0 is installed and the /endpoint/add-guest.php endpoint processes the 'name' parameter without applying htmlspecialchars or equivalent output encoding.
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 on the 'name' parameter in add-guest.php. Use server-side sanitization (e.g., htmlspecialchars with ENT_QUOTES) before rendering user input and consider implementing a Content Security Policy header.
- 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-6767 — 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-6767 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