Quick answers
- Is CVE-2025-67438 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-67438 being exploited in the wild.
- How severe is CVE-2025-67438?
- Medium severity, with a CVSS score of 4, published 20 February 2026.
- Which products and versions are affected?
- @sync-in/server (npm) SEMVER:introduced=0,fixed=1.9.3.
- Is there a fix for CVE-2025-67438?
- Yes. @sync-in/server (npm): upgrade to 1.9.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-67438 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-67438?
- Check whether you run @sync-in/server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @sync-in/server (npm): upgrade to 1.9.3 or later
npm install @sync-in/server@1.9.3
Technical details
This is a stored cross-site scripting (CWE-79) vulnerability in Sync-in Server prior to version 1.9.3. An authenticated attacker can upload a crafted SVG file containing embedded malicious JavaScript. When other users access or preview the SVG file, the browser executes the injected script in their security context, allowing session hijacking and data theft. The root cause was improper file content-type handling; the fix involves serving uploaded files with the `Content-Disposition: attachment` header to force download behavior instead of in-browser rendering. Authentication is required, but no special privileges are needed beyond user login status.
Affected products
- Sync-in Server before 1.9.3
Identifiers
- CVE-2025-67438
- GHSA-9jmq-xgjm-p8c2
Timeline
- 2026-02-20: disclosed
- 2025-12-07: patched: Fix committed on December 7, 2025; patched in version 1.9.3