Security readout for executives and security teams
Plain-English summary
CVE-2026-1147 is a cross-site scripting issue in Patients Waiting Area Queue Management System 1.0. An attacker with low privileges could manipulate the Reason field and potentially affect another user who views the resulting content. The public record says exploit details are public, but it is not listed in CISA KEV.
Executive priority
Treat as a moderate-priority web application issue. It is not currently known to be actively exploited, but public exploit availability raises the need to identify any deployed instances and reduce exposure. Prioritize systems reachable from untrusted networks or used by sensitive healthcare workflows.
Technical view
The issue affects /php/api_patient_schedule.php in SourceCodester/Patrick Mvuma Patients Waiting Area Queue Management System 1.0. Manipulation of the Reason argument leads to XSS. CVSS 4.0 is 5.1 with network attack vector, low complexity, low privileges required, and user interaction present. CWE-79 is the primary fit; CWE-94 is also listed.
Likely exposure
Exposure is likely limited to organizations running Patients Waiting Area Queue Management System 1.0, especially if accessible over a network to authenticated users. Public internet exposure increases operational risk, but the source bundle does not confirm broad deployment or default exposure.
Exploitation context
The CVE record says the attack can be initiated remotely and that exploit information has been made public. The CVSS vector requires low privileges and user interaction. There is no KEV listing and no cited evidence of active exploitation in the provided sources.
Researcher notes
The public description is concise and does not name a patch. The affected component is described as an unknown part of api_patient_schedule.php. Validate in a controlled, authorized environment only. Do not assume products beyond Patients Waiting Area Queue Management System 1.0 are affected without additional evidence.
Mitigation direction
- Identify whether version 1.0 is deployed anywhere in the environment.
- Check the vendor or project page for updated guidance or fixes.
- Restrict access to the application to trusted users and networks where possible.
- If maintaining the code, review handling of the Reason field for safe output encoding.
- Monitor application logs for unusual Reason field content.
Validation and detection
- Confirm application name, maintainer, and version against asset inventory.
- Verify whether /php/api_patient_schedule.php exists in deployed instances.
- Review source or configuration for how the Reason parameter is stored and displayed.
- Check logs for suspicious submissions to patient scheduling functionality.
- Track CVE and VulDB references for patch or advisory updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1147 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.1 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
5.1MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
Source materials
- CVE List V5 sourceCVE List V5
- VDB-341740 | SourceCodester/Patrick Mvuma Patients Waiting Area Queue Management System api_patient_schedule.php cross site scriptingCVE reference · vdb-entry, technical-description
- VDB-341740 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #735544 | Patrick Mvuma Patients Waiting Area Queue Management System 1.0 Cross Site ScriptingCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.