LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36011: A cross-site scripting (XSS) issue in Add Patient Form in QDOCS Smart Hospital Management System 3.1 allows...

A cross-site scripting (XSS) issue in Add Patient Form in QDOCS Smart Hospital Management System 3.1 allows a remote attacker to inject arbitrary code via the Name, Guardian Name, Email, Address, Remarks, or Any Known Allergies field.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-36011 is an XSS flaw in the Add Patient Form of QDOCS Smart Hospital Management System 3.1. A remote attacker may inject script through patient-related text fields. Business risk depends on whether this product is deployed and who views submitted records.

Executive priority

Prioritize investigation if QDOCS Smart Hospital Management System 3.1 is used in patient workflows or exposed beyond trusted staff. Urgency is constrained by missing severity and patch data.

Technical view

The CVE describes cross-site scripting through Name, Guardian Name, Email, Address, Remarks, or Any Known Allergies fields in the Add Patient Form. No CVSS, CWE, patch, authentication requirement, or affected CPE data is provided in the source bundle.

Likely exposure

Organizations using QDOCS Smart Hospital Management System 3.1 may be exposed, especially if the Add Patient Form is reachable by untrusted users. The bundle does not establish exposure for other versions or products.

Exploitation context

The CVE is not listed as KEV, so active exploitation is not supported by the provided evidence. A public Exploit-DB reference exists, indicating public technical disclosure, but the bundle does not prove real-world exploitation.

Researcher notes

Evidence is thin: the record names vulnerable fields and an Exploit-DB reference, but lacks CVSS, CWE, CPEs, auth context, patch status, and exploit-in-the-wild confirmation. Avoid extrapolating impact beyond browser-side XSS risk.

Mitigation direction

  • Check QDOCS vendor guidance for fixed versions or official mitigations.
  • Restrict Add Patient Form access to trusted users where possible.
  • Review input validation and output encoding around the listed patient fields.
  • Monitor application logs for suspicious submissions in affected fields.

Validation and detection

  • Inventory whether QDOCS Smart Hospital Management System 3.1 is deployed.
  • Identify whether the Add Patient Form is externally reachable.
  • Review vendor release notes or support channels for patch status.
  • Confirm stored patient-field content is safely encoded when rendered.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-36011 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
2Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.