Security readout for executives and security teams
Plain-English summary
OpenEyes 3.5.1 has a stored XSS issue in patient address handling. An attacker who can update patient details could store script or HTML in Address1, causing it to run when someone opens the patient profile. In a clinical system, this can affect user trust and session safety.
Executive priority
Prioritize if OpenEyes 3.5.1 is used in production clinical workflows. The issue is not shown as actively exploited, but stored XSS in patient records can affect staff accounts and sensitive workflows once malicious content is saved.
Technical view
The CVE describes stored cross-site scripting in Apperta Foundation OpenEyes 3.5.1. The vulnerable data path is patient-detail update to the Address1 parameter, with execution occurring later when the patient profile loads. No CVSS, CWE, fixed version, or vendor mitigation is provided in the supplied sources.
Likely exposure
Exposure appears limited to deployments of OpenEyes 3.5.1 where users or attackers can modify patient Address1 data and another user later views the affected profile. The bundle does not identify other affected versions or products.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. A public GitHub reference exists, so defenders should treat details as publicly discoverable, but exploitation in the wild is not established by the supplied sources.
Researcher notes
Evidence is sparse: the CVE text names OpenEyes 3.5.1, Address1, and stored execution on patient profile load. No CVSS vector, CWE, patch version, or vendor advisory details are present in the supplied bundle.
Mitigation direction
- Check Apperta/OpenEyes guidance for supported fixed versions or mitigations.
- Restrict patient-detail editing to trusted, authenticated users.
- Review patient Address1 fields for suspicious HTML or script content.
- Monitor OpenEyes sessions for unusual profile-view or account activity.
- For custom forks, confirm address fields are safely rendered.
Validation and detection
- Inventory OpenEyes deployments and confirm whether version 3.5.1 is present.
- Review whether patient Address1 data accepts stored markup.
- Check profile rendering for unsafe stored content execution risk.
- Verify access controls around patient-detail update workflows.
- Document findings against CVE-2021-40374 for remediation tracking.
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.
CVE-2021-40374 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://openeyes.apperta.org/CVE reference · x_refsource_MISC
- https://github.com/DCKento/CVE-2021-40374CVE reference · x_refsource_MISC
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.