CVE-2023-24187: An XML External Entity (XXE) vulnerability in ureport v2.2.9 allows attackers to execute arbitrary code via...
An XML External Entity (XXE) vulnerability in ureport v2.2.9 allows attackers to execute arbitrary code via uploading a crafted XML file to /ureport/designer/saveReportFile.
Security readout for executives and security teams
Plain-English summary
CVE-2023-24187 is a high-severity XML parsing flaw in ureport v2.2.9. A crafted XML upload to the report designer save endpoint is reported to enable arbitrary code execution. This matters most where ureport is deployed in business applications and the designer/upload function is reachable by untrusted or lightly trusted users.
Executive priority
Prioritize assessment for any externally reachable or broadly accessible ureport deployment. If ureport v2.2.9 is not present, business risk is low. If present with exposed designer upload functionality, treat remediation or access restriction as urgent because reported impact includes full system compromise.
Technical view
The CVE describes an XXE vulnerability, CWE-611, in ureport v2.2.9 at /ureport/designer/saveReportFile. The CVSS 3.1 score is 7.8 with high confidentiality, integrity, and availability impact. Source metadata lists local attack vector and user interaction required, while the description references an upload endpoint, so exposure should be verified in each deployment.
Likely exposure
Likely limited to environments running ureport v2.2.9 with the report designer save/upload path present. The CVE record does not provide CPEs, vendor package identifiers, or a fixed version, so asset confirmation requires internal inventory and application review.
Exploitation context
Public vulnerability write-ups are referenced, but the source bundle does not show confirmed active exploitation. The CVE is not marked as CISA KEV. Treat reachable designer/upload functionality as higher risk until vendor guidance and local exposure are confirmed.
Researcher notes
Evidence is sparse. The CVE names ureport v2.2.9 and an endpoint, but affected vendor/product fields are unspecified and no official patch is cited. The CVSS vector appears inconsistent with the HTTP endpoint wording. Validate version, reachability, authentication, and XML parser behavior without relying solely on CVSS metadata.
Mitigation direction
Inventory applications for ureport v2.2.9 usage.
Check the ureport project and vendor guidance for fixed versions or configuration advice.
Limit access to /ureport/designer/saveReportFile where operationally feasible.
Restrict report designer functions to trusted administrative users.
Monitor for unexpected XML uploads to the report designer endpoint.
Validation and detection
Confirm whether ureport v2.2.9 is present in deployed applications.
Verify whether /ureport/designer/saveReportFile is reachable by untrusted users.
Review application logs for suspicious XML upload activity.
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 · low confidence lookup
CWE-611: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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.
1CVSS vectors
3Timeline events
2ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-611 · source CWE mapping
Improper Restriction of XML External Entity Reference
Improper Restriction of XML External Entity Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.