# CVE-2026-41465: ProjeQtor < 12.4.4 Path Traversal via dynamicDialog.php

> Authenticated attackers can exploit a path traversal flaw in the log viewer to read arbitrary log files from the server filesystem.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 27 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-5m4x-rvj4-r2rw

## What is CVE-2026-41465?

CVE-2026-41465 is a high-severity path traversal vulnerability in ProjeQtor, published on 27 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ProjeQtor versions 7.0 through 12.4.3 contain a path traversal vulnerability in the log file viewer at dynamicDialog.php where the logname parameter is not validated against directory traversal sequences before constructing file paths. Authenticated attackers can inject directory traversal sequences ../ into the logname parameter to read arbitrary .log files accessible to the web server process on the filesystem.

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

## Which versions are affected by CVE-2026-41465?


## How do I fix CVE-2026-41465?

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

## Is CVE-2026-41465 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41465 and fix it if it is affected.

What it is: CVE-2026-41465 is a high-severity path traversal vulnerability in ProjeQtor, published on 27 Apr 2026. 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-2026-41465 exists.

Affected product: ProjeQtor. 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-2026-41465/ (Markdown: https://insights.sbomify.com/CVE-2026-41465/index.md)
```

## Sources

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

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