CVE-2025-25925: A stored cross-scripting (XSS) vulnerability in Openmrs v2.4.3 Build 0ff0ed allows attackers to execute arb...
A stored cross-scripting (XSS) vulnerability in Openmrs v2.4.3 Build 0ff0ed allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the personName.middleName parameter at /openmrs/admin/patients/shortPatientForm.form.
Security readout for executives and security teams
Plain-English summary
This is a stored XSS issue in OpenMRS v2.4.3 Build 0ff0ed. A highly privileged user could save script-like content in a patient middle-name field, which may later run in another user’s browser. Business impact is limited but relevant for healthcare portals because it can affect user trust and sensitive workflows.
Executive priority
Treat as a moderate hygiene and patient-system trust issue. Prioritize verification where OpenMRS is internet-accessible or used by many staff, but this does not indicate an emergency without evidence of active exploitation or unauthenticated access.
Technical view
CVE-2025-25925 is CWE-79 stored XSS in OpenMRS through the personName.middleName parameter at /openmrs/admin/patients/shortPatientForm.form. CVSS 3.1 is 4.8: network reachable, low complexity, high privileges required, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.
Likely exposure
Exposure appears limited to OpenMRS v2.4.3 Build 0ff0ed instances where privileged users can access the patient short form. The CVE record’s affected product metadata is incomplete, so broader version exposure is not established by the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates exploitation requires high privileges and another user viewing affected content, which lowers urgency compared with unauthenticated XSS.
Researcher notes
Evidence is narrow: the CVE cites one OpenMRS 2.4.3 Build 0ff0ed stored XSS path and a GitHub disclosure reference. Patch status, complete affected-version range, and exploitation in the wild are not established in the supplied bundle.
Mitigation direction
Check OpenMRS guidance for affected versions and fixed releases.
Upgrade or patch if vendor guidance identifies a remediation.
Restrict patient administration access to trusted, necessary users.
Review output encoding for stored patient-name fields.
Monitor audit logs for unusual patient-name edits.
Validation and detection
Inventory OpenMRS deployments and confirm exact version and build.
Confirm whether patient short-form access is limited to authorized staff.
Review rendered patient-name views for proper output encoding.
Check audit logs for suspicious middle-name changes.
Track OpenMRS advisories for CVE-2025-25925 remediation details.
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.
cwe · medium confidence lookup
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.
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.
We 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.