CVE-2026-36324
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 · uneditedSourceCodester Doctor Appointment System 1.0 is vulnerable to Cross Site Scripting (XSS) due to improper handling of user supplied input in the user registration functionality in register.php.
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 · high confidenceSourceCodester Doctor Appointment System 1.0 contains a reflected Cross Site Scripting (XSS) vulnerability in the user registration page (register.php). The application fails to properly sanitize or encode user-supplied input submitted during the registration process, 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.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the application and versionLocate the application files and check for version indicators such as a version.php file, README, or footer/version info in the application. For SourceCodester Doctor Appointment System, check the root directory for version files or examine the main index.php for version strings.Affected if The installed version is 1.0 of SourceCodester Doctor Appointment System
-
Verify register.php existsLocate the register.php file in the web application directory structure. Common paths include the root directory or a /users/ subdirectory.Affected if The register.php file exists and is accessible via the web server
-
Check if user registration is enabledAttempt to access the registration page via HTTP request (e.g., GET to /register.php or /index.php?page=register). Alternatively, examine the source code to determine if registration functionality is conditionally enabled.Affected if The registration functionality is enabled and accessible to unauthenticated users
-
Inspect registration input handling in codeOpen register.php in a text editor and examine how user-supplied input (username, email, name, etc.) is processed. Look for lack of htmlspecialchars(), htmlentities(), or other output encoding functions before displaying back user data.Affected if User input from registration is echoed back without proper encoding (e.g., no htmlspecialchars with ENT_QUOTES)
-
Check admin/staff data viewing pagesIdentify pages where administrators or staff view user registration data (e.g., admin/users.php, admin/registrations.php). Examine these files to see if they display registration information without encoding.Affected if Admin/staff panels display registration data without output encoding, allowing stored XSS to execute
A user is affected if they are running SourceCodester Doctor Appointment System version 1.0 with the registration functionality enabled and the registration data is viewable by administrators or staff without proper 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 strict input validation on all registration form fields and apply proper output encoding when rendering user data to prevent script injection. Consider implementing a Content Security Policy (CSP) header as an additional defense-in-depth measure.
- 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-2026-36324 — 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-2026-36324 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