Skip to content
Fencer Intel
high 7.5

CVE-2019-8903 in the critical feed json

Path Traversal in total.js

published 7y ago modified 4mo ago also GHSA-3q32-j57w-q4w7 , EUVD-2019-0211

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
72.1%
EPSS 72.1% chance of exploitation in 30 days, percentile 99.4%
public exploits
1
Metasploit, plus a Nuclei check

Summary

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

Patch / fix

  • npm total.js 3.2.3
  • totaljs total.js 3.2.3

Is CVE-2019-8903 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit auxiliary/scanner/http/totaljs_traversal)
  2. Published

Exploit prediction

72.06% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm total.js
<3.2.3
3.2.3

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.