# CVE-2024-11992: Path traversal vulnerability in Quick.CMS

> Remote attackers can exploit path traversal in Quick.CMS to read or delete arbitrary files on the server via the admin interface.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 29 Nov 2024
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-mcwr-8p82-73rf

## What is CVE-2024-11992?

CVE-2024-11992 is a critical path traversal vulnerability in Quick.CMS, published on 29 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Absolute path traversal vulnerability in Quick.CMS, version 6.7, the exploitation of which could allow remote users to bypass the intended restrictions and download any file if it has the appropriate permissions outside of documentroot configured on the server via the aDirFiles%5B0%5D parameter in the admin.php page. This vulnerability allows an attacker to delete files stored on the server due to a lack of proper verification of user-supplied input.

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

## Which versions are affected by CVE-2024-11992?


## How do I fix CVE-2024-11992?

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

## Is CVE-2024-11992 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11992 and fix it if it is affected.

What it is: CVE-2024-11992 is a critical path traversal vulnerability in Quick.CMS, published on 29 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11992 in the wild and no public exploit code.

Affected product: Quick.CMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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