# CVE-2019-15954: Total.js CMS RCE Vulnerability

> Authenticated users with widget privileges can execute arbitrary code on the server by injecting JavaScript into widget tags, bypassing sandbox restrictions.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v287-9w3v-x5c5

## What is CVE-2019-15954?

CVE-2019-15954 is a critical code injection vulnerability in n/a, published on 5 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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>

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2019-15954?

2 open source packages ship an affected version, including total4. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `total4` | npm | All versions | None |
| `total4` | npm | All versions | None |

Products: Totaljs Total.js Cms.

## How do I fix CVE-2019-15954?

No fix has been published for CVE-2019-15954 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-15954 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-15954 exists.

Public exploit code:

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

## Other vulnerabilities in n/a

- [CVE-2019-15952](https://insights.sbomify.com/CVE-2019-15952/): Total.js CMS Path Traversal (high 8.8)
- [CVE-2019-15953](https://insights.sbomify.com/CVE-2019-15953/): Total.js CMS Unauthorized Access (high 8.8)
- [CVE-2020-9381](https://insights.sbomify.com/CVE-2020-9381/): Code injection in n/a (high 7.5)
- [CVE-2019-15955](https://insights.sbomify.com/CVE-2019-15955/): Weak cryptography in n/a (medium 6.5)
- [CVE-2019-10260](https://insights.sbomify.com/CVE-2019-10260/): Moderate severity vulnerability that affects total.js (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15954 and fix it if it is affected.

What it is: CVE-2019-15954 is a critical code injection vulnerability in n/a, published on 5 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-15954 exists.

Affected packages and fixed versions:
- total4 (npm): affected all versions; no fix listed
- total4 (npm): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-15954/ (Markdown: https://insights.sbomify.com/CVE-2019-15954/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-15954
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-15954
- OSV: https://osv.dev/vulnerability/CVE-2019-15954

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-15954/
Summaries are generated and may contain mistakes; the official description above is the record.