","image":"https://o3.security/opengraph.png","datePublished":"2022-05-24T16:55:31Z","dateModified":"2023-11-08T04:01:15.614045Z","url":"https://o3.security/vulnerability/CVE-2019-15954","inLanguage":"en","author":{"@id":"https://o3.security/#organization"},"publisher":{"@id":"https://o3.security/#organization"},"mainEntityOfPage":{"@type":"WebPage","@id":"https://o3.security/vulnerability/CVE-2019-15954"},"speakable":{"@type":"SpeakableSpecification","cssSelector":["h1",".vuln-summary",".vuln-severity",".vuln-mitigation"]},"about":[{"@type":"SoftwareApplication","name":"total4","applicationCategory":"npm"}],"citation":[{"@type":"CreativeWork","name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2019-15954"},{"@type":"CreativeWork","name":"OSV.dev","url":"https://osv.dev/vulnerability/CVE-2019-15954"},{"@type":"CreativeWork","name":"FIRST.org EPSS","url":"https://www.first.org/epss/api-data?cve=CVE-2019-15954"},{"@type":"CreativeWork","url":"https://github.com/beerpwn/CVE/blob/master/Totaljs_disclosure_report/report_final.pdf"},{"@type":"CreativeWork","url":"https://seclists.org/fulldisclosure/2019/Sep/5"},{"@type":"CreativeWork","url":"http://packetstormsecurity.com/files/154924/Total.js-CMS-12-Widget-JavaScript-Code-Injection.html"}]}","url":"https://o3.security/vulnerability/CVE-2019-15954","identifier":"CVE-2019-15954","datePublished":"2022-05-24T16:55:31Z","dateModified":"2023-11-08T04:01:15.614045Z","inLanguage":"en","license":"https://creativecommons.org/licenses/by/4.0/","keywords":["CVE-2019-15954","CRITICAL severity","CWE-862","CVE","vulnerability","security advisory"],"creator":{"@id":"https://o3.security/#organization"},"isAccessibleForFree":true,"citation":[{"@type":"CreativeWork","name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2019-15954"},{"@type":"CreativeWork","name":"OSV.dev","url":"https://osv.dev/vulnerability/CVE-2019-15954"},{"@type":"CreativeWork","name":"FIRST.org EPSS","url":"https://www.first.org/epss/api-data?cve=CVE-2019-15954"}],"variableMeasured":[{"@type":"PropertyValue","name":"CVSS Base Score","value":9.9,"description":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"},{"@type":"PropertyValue","name":"Severity","value":"CRITICAL"},{"@type":"PropertyValue","name":"EPSS Percentile","value":100}]}`"}},{"@type":"Question","name":"How severe is CVE-2019-15954?","acceptedAnswer":{"@type":"Answer","text":"CVE-2019-15954 has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended."}},{"@type":"Question","name":"Which packages are affected by CVE-2019-15954?","acceptedAnswer":{"@type":"Answer","text":"CVE-2019-15954 affects the following packages: total4 (npm). Ecosystems affected: npm."}},{"@type":"Question","name":"How do I fix CVE-2019-15954?","acceptedAnswer":{"@type":"Answer","text":"The records we use list no patched version of total4 for CVE-2019-15954. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range."}},{"@type":"Question","name":"How do I detect CVE-2019-15954 in my npm dependencies?","acceptedAnswer":{"@type":"Answer","text":"Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for total4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version."}},{"@type":"Question","name":"How do I mitigate CVE-2019-15954 if there is no patch (or I can't update yet)?","acceptedAnswer":{"@type":"Answer","text":"Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used."}},{"@type":"Question","name":"Is CVE-2019-15954 actively exploited in the wild?","acceptedAnswer":{"@type":"Answer","text":"Yes. There are 5 known exploit references for CVE-2019-15954, including 1 documented proof-of-concept exploit on Exploit-DB and 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization."}},{"@type":"Question","name":"What is the EPSS score for CVE-2019-15954?","acceptedAnswer":{"@type":"Answer","text":"CVE-2019-15954 has an EPSS (Exploit Prediction Scoring System) score of 78.7%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended."}},{"@type":"Question","name":"What type of vulnerability is CVE-2019-15954?","acceptedAnswer":{"@type":"Answer","text":"CVE-2019-15954 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation."}},{"@type":"Question","name":"Is there exploit tooling available for CVE-2019-15954?","acceptedAnswer":{"@type":"Answer","text":"A Metasploit module references CVE-2019-15954, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments."}},{"@type":"Question","name":"When was CVE-2019-15954 published, and has it been updated?","acceptedAnswer":{"@type":"Answer","text":"CVE-2019-15954 was published on May 24, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting."}}]}
NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2019-15954 — total4

CRITICAL

CVE-2019-15954 is a critical-severity (CVSS 9.9) CWE-862 vulnerability in total4. 5 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Total.js CMS RCE Vulnerability

Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
5 known
Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
78.7%probability of exploitation in next 30 days
Very High Risk0.00%
Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk
50.2%62.1%74.0%85.9%56.9%78.7%May 26Aug 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

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.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
total4npm
4Kdownloads / week

Description

An issue was discovered in Total.js CMS 12.0.0. An authenticated user with the widgets privilege can gain achieve Remote Command Execution (RCE) on the remote server by creating a malicious widget with a special tag containing JavaScript code that will be evaluated server side. In the process of evaluating the tag by the back-end, it is possible to escape the sandbox object by using the following payload: <script total>global.process.mainModule.require(child_process).exec(RCE);</script>

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmtotal4all versionsNo fix

Affected Products

1 product · 1 configurations
Application
total.js cmstotaljs
1 version
12.0.0
Exploits & PoCs
5

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

EDB-47531remotemultiple✓ Verified

Total.js CMS 12 - Widget JavaScript Code Injection (Metasploit)

by Metasploit · Oct 22, 2019

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Remediation status

    The records we use list no patched version of total4 for CVE-2019-15954. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

An issue was discovered in Total.js CMS 12.0.0. An authenticated user with the widgets privilege can gain achieve Remote Command Execution (RCE) on the remote server by creating a malicious widget with a special tag containing JavaScript code that will be evaluated server side. In the process of evaluating the tag by the back-end, it is possible to escape the sandbox object by using the following payload: `<script total>global.process.mainModule.require(child_process).exec(RCE);</script>`
O3 Security · Impact-Aware SCA

Is CVE-2019-15954 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2019-15954: total4: Total.js CMS RCE Vulnerability