# CVE-2020-36970: PMB 5.6 - 'chemin' Local File Disclosure

> Attackers can read arbitrary system files via path traversal in getgif.php, exposing sensitive data in PMB library software.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 28 Jan 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-mc39-mcp7-82wg

## What is CVE-2020-36970?

CVE-2020-36970 is a medium-severity path traversal vulnerability in PMB Services, published on 28 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PMB 5.6 contains a local file disclosure vulnerability in getgif.php that allows attackers to read arbitrary system files by manipulating the 'chemin' parameter. Attackers can exploit the unsanitized file path input to access sensitive files like /etc/passwd by sending crafted requests to the getgif.php endpoint.

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

## Which versions are affected by CVE-2020-36970?


## How do I fix CVE-2020-36970?

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

## Is CVE-2020-36970 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36970 and fix it if it is affected.

What it is: CVE-2020-36970 is a medium-severity path traversal vulnerability in PMB Services, published on 28 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36970 in the wild and no public exploit code.

Affected product: PMB Services. 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-2020-36970/ (Markdown: https://insights.sbomify.com/CVE-2020-36970/index.md)
```

## Sources

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

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