LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10571: Multiple reflected cross-site scripting (XSS) vulnerabilities in OpenEMR before 5.0.1 allow remote attacker...

Multiple reflected cross-site scripting (XSS) vulnerabilities in OpenEMR before 5.0.1 allow remote attackers to inject arbitrary web script or HTML via the (1) patient parameter to interface/main/finder/finder_navigation.php; (2) key parameter to interface/billing/get_claim_file.php; (3) formid or (4) formseq parameter to interface/orders/types.php; (5) eraname, (6) paydate, (7) post_to_date, (8) deposit_date, (9) debug, or (10) InsId parameter to interface/billing/sl_eob_process.php; (11) form_source, (12) form_paydate, (13) form_deposit_date, (14) form_amount, (15) form_name, (16) form_pid, (17) form_encounter, (18) form_date, or (19) form_to_date parameter to interface/billing/sl_eob_search.php; (20) codetype or (21) search_term parameter to interface/de_identification_forms/find_code_popup.php; (22) search_term parameter to interface/de_identification_forms/find_drug_popup.php; (23) search_term parameter to interface/de_identification_forms/find_immunization_popup.php; (24) id parameter to interface/forms/CAMOS/view.php; (25) id parameter to interface/forms/reviewofs/view.php; or (26) list_id parameter to library/custom_template/personalize.php.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-10571 is a set of reflected XSS flaws in OpenEMR before 5.0.1. An attacker could cause malicious script or HTML to run in a user's browser through vulnerable request parameters. For healthcare systems, this matters because browser sessions may expose sensitive patient or billing workflows.

Executive priority

Treat this as a patch and exposure-reduction item for any legacy OpenEMR deployment. It is not supported as actively exploited by the provided evidence, but patient-facing healthcare workflows make browser compromise materially sensitive.

Technical view

The CVE lists 26 reflected XSS vectors across OpenEMR PHP routes in finder navigation, billing, orders, de-identification popups, forms, and custom template personalization. The sources identify OpenEMR before 5.0.1 and reference the related issue, pull request, and commit. No CVSS, CWE, or CPE data is included.

Likely exposure

Exposure is likely limited to organizations running OpenEMR before 5.0.1. Risk increases when OpenEMR is internet-accessible or used by privileged clinical, billing, or administrative users. The source bundle does not provide exact CPEs or deployment prerequisites.

Exploitation context

The CVE says remote attackers can inject script or HTML through reflected parameters. It is not listed in CISA KEV, and the provided sources do not establish active exploitation. Reflected XSS generally depends on a vulnerable user interaction path.

Researcher notes

The record is source-rich for vulnerable parameters and file paths, but weak on scoring metadata. Focus validation on version confirmation, route reachability, and whether local customizations reintroduced unsafe reflection after the upstream fix.

Mitigation direction

  • Upgrade OpenEMR to version 5.0.1 or later using vendor guidance.
  • Review the referenced OpenEMR issue, pull request, and commit for fix scope.
  • Restrict external access to OpenEMR where operationally possible.
  • Harden session, MFA, and role controls for clinical and billing users.
  • Review custom templates or modified PHP routes for similar output handling.

Validation and detection

  • Inventory OpenEMR instances and confirm installed versions.
  • Confirm no production instance remains below OpenEMR 5.0.1.
  • Review web access controls for exposed OpenEMR interfaces.
  • Check application logs for unusual requests to listed vulnerable routes.
  • Use approved application testing in staging to confirm XSS remediation.
Prepared
Confidence
medium
Sources
7

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.

cve · low confidence lookup

CVE-2018-10571 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
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

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.