CVE-2022-36547
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 · uneditedEdoc-doctor-appointment-system v1.0.1 was discovered to contain a reflected cross-site scripting (XSS) vulnerability at /patient/index.php. This vulnerability allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Search field.
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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in the Edoc-doctor-appointment-system v1.0.1 at /patient/index.php. The Search field does not properly sanitize user input, allowing attackers to inject malicious JavaScript or HTML code that executes in the victim's browser when the crafted payload is submitted.
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.0.1CVSS 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 Edoc Doctor Appointment System is installedLocate the web application files on the server, typically in the web root directory. Look for the presence of the 'patient' directory and index.php file.Affected if The application files exist on the server in the expected web directory structure.
-
Verify the application version is 1.0.1Search for version indicators in application files, such as a version.php file, changelog, readme, or any configuration file that lists the software version. Compare your installed version against the affected range.Affected if The installed version is exactly 1.0.1.
-
Check if patient/index.php existsLocate and inspect the file at /patient/index.php within the application web root. Confirm the file is present and accessible via the web server.Affected if The file /patient/index.php exists in the application.
-
Identify the Search field in patient/index.phpOpen patient/index.php in a text editor or use grep to search for form input fields with 'search' in the name attribute. Examine the code handling this Search parameter.Affected if The Search input field exists in patient/index.php.
-
Inspect Search field for input sanitizationExamine the PHP code in patient/index.php that processes the Search parameter. Look for whether the input is passed through sanitization functions like htmlspecialchars, strip_tags, or similar escaping functions before being output.Affected if The Search parameter is not sanitized before being rendered in the page output (no htmlspecialchars or equivalent escaping is applied).
You are affected if you are running Edoc Doctor Appointment System version 1.0.1 and the Search field in patient/index.php lacks proper input sanitization, allowing reflected XSS.
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 input validation and output encoding on the Search field in patient/index.php. All user-supplied data should be sanitized using appropriate escaping functions (such as htmlspecialchars in PHP) before being rendered in HTML output.
- 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-2022-36547 — 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-2022-36547 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