dbcve.org
Sante Pacs ServerApplication · Santesoft

CVE-2025-54759

MEDIUM · 6.1 CVSS v3.1 Published 2025-08-18
Fix available
A fix is available. Upgrade to 4.2.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Sante PACS Server is vulnerable to stored cross-site scripting. An attacker could inject malicious HTML codes redirecting a user to a malicious webpage and stealing the user's cookie.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Sante PACS Server contains a stored cross-site scripting (XSS) vulnerability where malicious HTML or JavaScript code can be injected into the application and persisted. When other users view the injected content, the malicious script executes, enabling session hijacking via cookie theft and redirection to attacker-controlled webpages.

MitigationImplement strict input validation and output encoding/encoding on all user-supplied data, deploy Content-Security-Policy headers to prevent script execution, and sanitize any stored content before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sante Pacs ServerApplication
Affected:< 4.2.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Sante PACS Server version
    Access the application admin panel or check the software documentation for the About/Version section. If you have server access, check the installed software package or registry entry for the version number.
    Affected if The displayed version is lower than 4.2.3 (e.g., 4.2.0, 4.1.x, or earlier)
  2. Determine if the web interface is accessible
    Attempt to access the Sante PACS Server web portal via browser at the expected URL (commonly https://localhost:8080 or similar depending on your configuration).
    Affected if The web interface is reachable and accepts user input in any field (patient data, comments, notes, or administrative fields)
  3. Identify user input fields that store and display data
    Navigate through the application and locate fields where users can enter and save text data that is later displayed back to users (such as patient notes, study descriptions, user profile fields, or administrative configuration inputs).
    Affected if Any field accepts text input and persists it for display to other users without visible sanitization indicators
  4. Review stored data for potential XSS payloads
    Query the application's database or use the administrative interface to view stored records containing user-supplied text. Inspect the HTML source of pages displaying stored content to identify any unescaped HTML or JavaScript characters.
    Affected if Stored data contains raw HTML tags (<script>, <img>, <iframe>, or event handlers like onload/onerror) or JavaScript code that executes when viewed

You are affected if your Sante PACS Server version is below 4.2.3 AND the web interface is accessible with fields that accept and display user-supplied text content to other users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.2.3 or later
Fixed in 4.2.3
Interim mitigation

Implement strict input validation and output encoding/encoding on all user-supplied data, deploy Content-Security-Policy headers to prevent script execution, and sanitize any stored content before rendering.

Recommended fix High confidence

4.2.3

  1. Backup the current Sante PACS Server installation and database
  2. Download Sante PACS Server version 4.2.3 or later from the official vendor website (www.santesoft.com)
  3. Stop the Sante PACS Server service
  4. Install the new version following the vendor's upgrade documentation
  5. Start the Sante PACS Server service
  6. Verify the upgrade was successful and confirm the vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sante Pacs Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54759 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data