# CVE-2022-42188: Lavalite vulnerable to Arbitrary File Read via Directory Traversal

> Attackers can exploit path traversal in the XSRF-TOKEN cookie to read arbitrary files on the server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2022
- **Updated:** 13 May 2025
- **Also known as:** GHSA-cm22-88qr-7ffh

## What is CVE-2022-42188?

CVE-2022-42188 is a high-severity path traversal vulnerability in n/a, published on 18 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Lavalite 9.0.0, the XSRF-TOKEN cookie is vulnerable to path traversal attacks, enabling read access to arbitrary files on the server.

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

## Which versions are affected by CVE-2022-42188?

2 open source packages ship an affected version, including lavalite/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lavalite/cms` | Packagist | All versions | None |
| `lavalite/cms` | Packagist | All versions | None |

Products: Lavalite Lavalite.

## How do I fix CVE-2022-42188?

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

## Is CVE-2022-42188 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-27238](https://insights.sbomify.com/CVE-2023-27238/): LavaLite vulnerable to web cache poisoning (critical 9.8)
- [CVE-2025-70866](https://insights.sbomify.com/CVE-2025-70866/): Auth bypass in n/a (high 8.8)
- [CVE-2023-36983](https://insights.sbomify.com/CVE-2023-36983/): Information disclosure in n/a (high 7.5)
- [CVE-2023-36984](https://insights.sbomify.com/CVE-2023-36984/): Information disclosure in n/a (high 7.5)
- [CVE-2024-31828](https://insights.sbomify.com/CVE-2024-31828/): Lavalite CMS Cross Site Scripting vulnerability (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-42188 and fix it if it is affected.

What it is: CVE-2022-42188 is a high-severity path traversal vulnerability in n/a, published on 18 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-42188 exists.

Affected packages and fixed versions:
- lavalite/cms (Packagist): affected all versions; no fix listed
- lavalite/cms (Packagist): 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-2022-42188/ (Markdown: https://insights.sbomify.com/CVE-2022-42188/index.md)
```

## Sources

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

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