# CVE-2019-15952: Total.js CMS Path Traversal

> Authenticated users can exploit path traversal to include arbitrary HTML files, enabling server-side template injection and remote code execution.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/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-pwvp-h579-hfxg

## What is CVE-2019-15952?

CVE-2019-15952 is a high-severity path traversal 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 Pages privilege can conduct a path traversal attack (../) to include .html files that are outside the permitted directory. Also, if a page contains a template directive, then the directive will be server side processed. Thus, if a user can control the content of a .html file, then they can inject a payload with a malicious template directive to gain Remote Command Execution. The exploit will work only with the .html extension.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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-15952?

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

## Is CVE-2019-15952 being exploited?

There is no known exploitation of CVE-2019-15952 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-15954](https://insights.sbomify.com/CVE-2019-15954/): Total.js CMS RCE Vulnerability (critical 9.9)
- [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-15952 and fix it if it is affected.

What it is: CVE-2019-15952 is a high-severity path traversal 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: There is no known exploitation of CVE-2019-15952 in the wild and no public exploit code.

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-15952/ (Markdown: https://insights.sbomify.com/CVE-2019-15952/index.md)
```

## Sources

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

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