CVE-2023-7238
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 · uneditedA XSS payload can be uploaded as a DICOM study and when a user tries to view the infected study inside the Osimis WebViewer the XSS vulnerability gets triggered. If exploited, the attacker will be able to execute arbitrary JavaScript code inside the victim's browser.
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 confidenceA stored XSS vulnerability in Osimis WebViewer allows attackers to embed malicious JavaScript payloads within DICOM study metadata. When legitimate users view the infected DICOM studies through the web interface, the XSS payload executes in their browsers, enabling arbitrary JavaScript execution.
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= 1.4.2.0-9d9eff4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Osimis WebViewer is installedCheck the Orthanc configuration file (orthanc.json) for the WebViewer plugin section, or query the Orthanc REST API at /plugins. Look for 'Osimis' or 'WebViewer' in the loaded plugins list.Affected if The WebViewer plugin is loaded and the version is 1.4.2.0-9d9eff4.
-
Determine the WebViewer versionAccess the Orthanc WebViewer about page (typically /webviewer/about or /osimis-webviewer), or check the Orthanc logs at startup which list loaded plugins with their versions.Affected if The version displayed matches 1.4.2.0-9d9eff4.
-
Verify the web interface is accessibleConfirm the Orthanc REST API is responding (try /system) and the WebViewer UI endpoint is reachable (usually /webviewer or /osimis-webviewer).Affected if The WebViewer web interface is exposed and available to users.
-
Inspect DICOM metadata for scriptable contentUse a DICOM tool (dcmtk, pydicom, or Orthanc's /studies/{id}/metadata) to query DICOM tags in stored studies. Check fields like PatientName (0010,0010), StudyDescription (0008,1030), SeriesDescription (0008,103E), and AccessionNumber (0008,0050) for HTML/script tags or encoded JavaScript patterns.Affected if Any DICOM study in the system contains unsanitized script tags or JavaScript payloads in metadata fields that render in the WebViewer.
-
Check recent upload logs for unvalidated studiesReview Orthanc upload logs or audit logs for DICOM imports, especially from untrusted sources or anonymous upload endpoints. Look for entries indicating studies were uploaded without prior sanitization.Affected if Studies were uploaded by untrusted or anonymous users without evidence of prior DICOM metadata validation.
You are affected if you are running Osimis WebViewer version 1.4.2.0-9d9eff4 AND any DICOM studies with malicious JavaScript payloads in metadata fields are present in your system and accessible through the web viewer.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict input validation and sanitization on DICOM file uploads to strip or neutralize scriptable content, and apply proper output encoding when rendering DICOM metadata in the web viewer.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-7238 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-7238 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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