Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Path Traversal in total.jsGHSA-3q32-j57w-q4w7

HIGHFix: totaljs/framework@c37cafb

GHSA-3q32-j57w-q4w7 is a high-severity (CVSS 7.5) Path Traversal vulnerability in total.js. 1 public exploit reference exists, so weaponization risk is real. A fix is available for total.js — see the affected versions and patch details below.

Also known asCVE-2019-8903
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
72.1%probability of exploitation in next 30 days
Very High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk
47.6%57.6%67.7%77.7%53.3%72.1%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-3q32-j57w-q4w7 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

10other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
total.jsnpm
504downloads / week

Description

Affected versions of total.js are vulnerable to Path Traversal. Due to insufficient input sanitization in URLs, attackers can access server files outside the /public folder by using relative paths.
The files served are limited to these file types: flac, jpg, jpeg, png, gif, ico, js, css, txt, xml, woff, woff2, otf, ttf, eot, svg, zip, rar, pdf, docx, xlsx, doc, xls, html, htm, appcache, manifest, map, ogv, ogg, mp4, mp3, webp, webm, swf, package, json, md, m4v, jsx, heif, heic.

Recommendation

  • If you are using version 2.1.x, upgrade to 2.1.1 or later.
  • If you are using version 2.2.x, upgrade to 2.2.1 or later.
  • If you are using version 2.3.x, upgrade to 2.3.1 or later.
  • If you are using version 2.4.x, upgrade to 2.4.1 or later.
  • If you are using version 2.5.x, upgrade to 2.5.1 or later.
  • If you are using version 2.6.x, upgrade to 2.6.3 or later.
  • If you are using version 2.7.x, upgrade to 2.7.1 or later.
  • If you are using version 2.8.x, upgrade to 2.8.1 or later.
  • If you are using version 2.9.x, upgrade to 2.9.5 or later.
  • If you are using version 3.0.x, upgrade to 3.0.1 or later.
  • If you are using version 3.1.x, upgrade to 3.1.1 or later.
  • If you are using version 3.2.x, upgrade to 3.2.4 or later.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmtotal.jsall versions3.2.3npm install total.js@3.2.3

Affected Products

1 product · 1 configurations
Application
total.jstotaljs
< 3.2.3
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

index.js in Total.js Platform before 3.2.3 allows path traversal.

github.comMetasploitOct 2020

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for total.js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update total.js to 3.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3q32-j57w-q4w7 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

How to detect GHSA-3q32-j57w-q4w7

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-3q32-j57w-q4w7 -u https://target
Template
Totaljs <3.2.3 - Local File Inclusion
Severity
high
Impact
An attacker can exploit this vulnerability to read sensitive files, execute arbitrary code, or launch further attacks.
Remediation
Upgrade Totaljs to version 3.2.3 or later to fix the LFI vulnerability.

Template by ProjectDiscovery nuclei-templates (madrobot), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

Affected versions of `total.js` are vulnerable to Path Traversal. Due to insufficient input sanitization in URLs, attackers can access server files outside the `/public` folder by using relative paths. The files served are limited to these file types: `flac`, `jpg`, `jpeg`, `png`, `gif`, `ico`, `js`, `css`, `txt`, `xml`, `woff`, `woff2`, `otf`, `ttf`, `eot`, `svg`, `zip`, `rar`, `pdf`, `docx`, `xlsx`, `doc`, `xls`, `html`, `htm`, `appcache`, `manifest`, `map`, `ogv`, `ogg`, `mp4`, `mp3`, `webp`, `webm`, `swf`, `package`, `json`, `md`, `m4v`, `jsx`, `heif`, `heic`. ## Recommendation - If
O3 Security · Impact-Aware SCA

Is GHSA-3q32-j57w-q4w7 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Path Traversal in total.js (High 7.5)