CVE-2025-55071
BaseFortify
Publication date: 2026-01-20
Last updated on: 2026-01-29
Assigner: Talos
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| meddream | pacs_server | 7.3.6.870 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not specify how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
CVE-2025-55071 is a reflected cross-site scripting (XSS) vulnerability in the modifyAnonymize functionality of MedDream PACS Premium 7.3.6.870. It occurs because the 'name' parameter in the Pacs/modifyAnonymize.php script is included directly in the HTML output without sanitization or encoding. This allows an attacker to craft a malicious URL that injects arbitrary JavaScript code, which executes in the victim's browser when they visit the URL. [1]
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute arbitrary JavaScript code in the context of a victim's browser, potentially leading to theft of sensitive information, session hijacking, or manipulation of the web application's content. It affects confidentiality and integrity with limited impact but does not affect availability. Exploitation requires user interaction by visiting a crafted URL. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending a specially crafted HTTP GET request to the vulnerable endpoint and observing if the injected script is reflected in the response. For example, you can use curl to test the vulnerability with the following command: curl -i "http://<target>/Pacs/modifyAnonymize.php?name=<script>alert(1)</script>" and check if the response contains the injected <script>alert(1)</script> code. If the script is reflected and executed in a browser, the vulnerability exists. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the vendor-provided patch released on December 5, 2025, which addresses this vulnerability. Until the patch is applied, restrict access to the vulnerable endpoint, implement web application firewall (WAF) rules to block malicious input patterns targeting the 'name' parameter, and educate users to avoid clicking on suspicious links that may exploit this reflected XSS vulnerability. [1]