dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-25860

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
OpenClinic GA 5.351.19 contains a reflected cross-site scripting vulnerability in the DICOM image upload handler that allows attackers to execute arbitrary JavaScript in a victim's browser by embedding malicious payloads in DICOM file metadata fields. Attackers can craft a DICOM file with JavaScript payloads in metadata fields such as Study Description, which are reflected without sanitization in popup.jsp and archiving/uploadfiles_jsp.java when processed through the Upload DICOM images feature.

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 · high confidence

OpenClinic GA 5.351.19 has a reflected XSS vulnerability in its DICOM image upload functionality. Attackers can embed JavaScript payloads in DICOM metadata fields (e.g., Study Description) which are then reflected without sanitization in popup.jsp and archiving/uploadfiles_jsp.java when users process uploaded DICOM files.

MitigationImplement input validation and output encoding for DICOM metadata fields before reflecting them in HTML pages. Sanitize or escape special characters in all DICOM metadata values before rendering in the JSP pages.

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

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. Verify OpenClinic GA installation
    Locate the OpenClinic GA web application directory. Common paths include /var/www/openclinic, C:\inetpub\openclinic, or within application server directories like Tomcat/webapps. Identify the version by checking version.txt, CHANGELOG.txt, or the application's about/Info page.
    Affected if OpenClinic GA version 5.351.19 or earlier is installed
  2. Confirm DICOM module is present
    Check for the DICOM-related components in the installation. Look for a 'dicom' folder or archive directory containing uploadfiles_jsp.java. Verify the presence of popup.jsp in the web root.
    Affected if The DICOM upload feature files (uploadfiles_jsp.java, popup.jsp) exist in the application
  3. Identify DICOM upload functionality access
    Access the OpenClinic GA web interface and navigate to the DICOM image upload section. This is typically found under Admin, Imaging, or DICOM menus depending on the installation. Record the URL path used for uploading.
    Affected if The Upload DICOM images feature is accessible and functional in the web interface
  4. Inspect affected source files for unsanitized output
    Examine popup.jsp and archiving/uploadfiles_jsp.java in the source code. Search for code that outputs DICOM metadata fields (particularly StudyDescription) directly to the response without using encoding functions like htmlEscape or similar sanitization.
    Affected if The source code directly outputs DICOM metadata fields without visible sanitization or encoding
  5. Verify DICOM metadata is reflected in responses
    Upload a test DICOM file with a benign payload in the Study Description field (e.g., <script>test</script>). Submit the upload and observe whether this value appears unsanitized in the resulting popup or page response.
    Affected if DICOM metadata values are reflected in the web interface without encoding

A user is affected if they run OpenClinic GA version 5.351.19 or earlier and have the DICOM upload feature accessible, with the application reflecting DICOM metadata fields without sanitization in the web interface.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation and output encoding for DICOM metadata fields before reflecting them in HTML pages. Sanitize or escape special characters in all DICOM metadata values before rendering in the JSP pages.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25860 — 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-2026-25860 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