Security readout for executives and security teams
Plain-English summary
OpenMRS Reporting Module 1.12.0 has a reported weakness where an attacker could abuse an administrator’s authenticated browser to place JavaScript into a report name field. That can turn normal report management pages into a browser-side attack surface for administrators.
Executive priority
Treat this as a targeted application-risk item, not an internet-wide emergency. Prioritize healthcare or clinical systems using OpenMRS Reporting Module 1.12.0, because administrator browser compromise can affect trust in operational reporting workflows.
Technical view
The CVE describes CSRF leading to XSS in OpenMRS Reporting Module 1.12.0. The affected location is webapp/reports/manageReports.jsp, where administrative authentication can be hijacked to insert JavaScript into a name field. The bundle provides no CVSS, CWE, or complete affected-version range.
Likely exposure
Exposure is likely limited to organizations running OpenMRS with Reporting Module 1.12.0, especially where administrators use the reporting management interface. The supplied affected-product metadata is incomplete, so confirm exposure through installed module inventory, not CPE matching.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Public references include a YouTube link and an OpenMRS GitHub commit link, but the bundle does not establish real-world exploitation or a complete remediation advisory.
Researcher notes
Evidence is sparse: the CVE description names Reporting Module 1.12.0 and manageReports.jsp, but structured affected data is listed as n/a. Do not extrapolate other OpenMRS modules or versions without vendor confirmation.
Mitigation direction
- Inventory OpenMRS instances for Reporting Module 1.12.0.
- Review OpenMRS guidance and the referenced upstream GitHub change.
- Upgrade or replace the module only according to confirmed vendor guidance.
- Restrict administrative report-management access while remediation is assessed.
Validation and detection
- Confirm the installed OpenMRS Reporting Module version on each instance.
- Check report name fields for unexpected script-like content.
- Review administrator activity around report-management pages.
- Verify vendor-confirmed fixes remove the CSRF-to-XSS condition.
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-2017-7990 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://www.youtube.com/watch?v=pfrIaNvIuFYCVE reference · x_refsource_MISC
- https://github.com/openmrs/openmrs-module-reporting/pull/141/commits/0023a659288538d2763835847d3414ecb18b931a#diff-50e25eddc5909110fa3d31090877c2fdCVE 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.