# CVE-2024-40112: Path traversal in n/a

> Attackers can manipulate the language cookie to include arbitrary files, disclosing sensitive information on Sitecom WLX-2006 range extenders.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2025
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-j3qf-mq3f-rgcf

## What is CVE-2024-40112?

CVE-2024-40112 is a medium-severity path traversal vulnerability in n/a, published on 2 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Local File Inclusion (LFI) vulnerability exists in Sitecom WLX-2006 Wall Mount Range Extender N300 v1.5 and before, which allows an attacker to manipulate the "language" cookie to include arbitrary files from the server. This vulnerability can be exploited to disclose sensitive information.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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

It affects 1 product.


Products: Sitecom Wlx-2006 Firmware.

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

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

## Is CVE-2024-40112 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-40113](https://insights.sbomify.com/CVE-2024-40113/): Hardcoded credentials in n/a (medium 6.5)
- [CVE-2024-40114](https://insights.sbomify.com/CVE-2024-40114/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-40112 is a medium-severity path traversal vulnerability in n/a, published on 2 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40112 exists.

Affected product: n/a. 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-40112/ (Markdown: https://insights.sbomify.com/CVE-2024-40112/index.md)
```

## Sources

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

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