# CVE-2012-5007: Path traversal in n/a

> Remote attackers can write to arbitrary PDF files in the Drupal Fill PDF module due to incorrect argument handling in the merge function.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 20 Sep 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4jq7-gcx7-hm85

## What is CVE-2012-5007?

CVE-2012-5007 is a medium-severity path traversal vulnerability in n/a, published on 20 Sep 2012. It can be exploited over the network.

### Official description

The Fill PDF module 7.x-1.x before 7.x-1.2 for Drupal allows remote attackers to write to arbitrary PDF files via unspecified vectors related to the fillpdf_merge_pdf function and incorrect arguments, a different vulnerability than CVE-2012-1625.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-264

## Which versions are affected by CVE-2012-5007?

It affects 1 product.


Products: Wizonesolutions Fillpdf.

## How do I fix CVE-2012-5007?

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

## Is CVE-2012-5007 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-1625](https://insights.sbomify.com/CVE-2012-1625/): Code injection in n/a (medium 6.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5007 and fix it if it is affected.

What it is: CVE-2012-5007 is a medium-severity path traversal vulnerability in n/a, published on 20 Sep 2012. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2012-5007 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-2012-5007/ (Markdown: https://insights.sbomify.com/CVE-2012-5007/index.md)
```

## Sources

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

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