# CVE-2007-5920: Path traversal in n/a

> Remote attackers can exploit a path traversal vulnerability in PicoFlat CMS to bypass authentication and upload files, leading to privilege escalation and potential code execution.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r9p2-4jr9-w24j

## What is CVE-2007-5920?

CVE-2007-5920 is a medium-severity path traversal vulnerability in n/a, published on 10 Nov 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

index.php in Domenico Mancini PicoFlat CMS before 0.4.18 allows remote attackers to include certain files via unspecified vectors, possibly due to a directory traversal vulnerability.  NOTE: this can be leveraged to bypass authentication and upload files by including pico_insert.php or unspecified other administrative scripts.  NOTE: some of these details are obtained from third party information.

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

## Which versions are affected by CVE-2007-5920?

It affects 1 product.


Products: Picoflat Cms Picoflat Cms.

## How do I fix CVE-2007-5920?

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

## Is CVE-2007-5920 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-5390](https://insights.sbomify.com/CVE-2007-5390/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5920 and fix it if it is affected.

What it is: CVE-2007-5920 is a medium-severity path traversal vulnerability in n/a, published on 10 Nov 2007. 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-2007-5920 in the wild and no public exploit code.

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

## Sources

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

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