# CVE-2011-5273: Path traversal in n/a

> Authenticated attackers can execute arbitrary PHP code via directory traversal in the package installer of DTC web applications.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **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:** 20 Mar 2014
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-f937-vggr-93fv

## What is CVE-2011-5273?

CVE-2011-5273 is a medium-severity path traversal vulnerability in n/a, published on 20 Mar 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in shared/package-installer in Domain Technologie Control (DTC) before 0.34.1 allows remote authenticated users to execute arbitrary PHP code via a .. (dot dot) in the pkg parameter in a do_install action to dtc/.

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

## Which versions are affected by CVE-2011-5273?

It affects 1 product.


Products: Gplhost Domain Technologie Control.

## How do I fix CVE-2011-5273?

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

## Is CVE-2011-5273 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-5274](https://insights.sbomify.com/CVE-2011-5274/): Command injection in n/a (high 7.5)
- [CVE-2011-5275](https://insights.sbomify.com/CVE-2011-5275/): Privilege escalation in n/a (high 7.5)
- [CVE-2011-0434](https://insights.sbomify.com/CVE-2011-0434/): SQL injection in n/a (high 7.5)
- [CVE-2009-0402](https://insights.sbomify.com/CVE-2009-0402/): SQL injection in n/a (high 7.5)
- [CVE-2011-3195](https://insights.sbomify.com/CVE-2011-3195/): Command injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-5273 and fix it if it is affected.

What it is: CVE-2011-5273 is a medium-severity path traversal vulnerability in n/a, published on 20 Mar 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-5273 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-2011-5273/ (Markdown: https://insights.sbomify.com/CVE-2011-5273/index.md)
```

## Sources

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

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