# CVE-2015-2209: Information disclosure in n/a

> Remote attackers can obtain the installation path via the c parameter in index.php, exposing sensitive server configuration details.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-75fx-h893-3mjw

## What is CVE-2015-2209?

CVE-2015-2209 is a medium-severity vulnerability in n/a, published on 4 Mar 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DLGuard 4.5 allows remote attackers to obtain the installation path via the c parameter to index.php.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2015-2209?

It affects 1 product.


Products: Dlguard Dlguard.

## How do I fix CVE-2015-2209?

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

## Is CVE-2015-2209 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-2066](https://insights.sbomify.com/CVE-2015-2066/): SQL injection in n/a (high 7.5)
- [CVE-2015-2064](https://insights.sbomify.com/CVE-2015-2064/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2011-5115](https://insights.sbomify.com/CVE-2011-5115/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2209 and fix it if it is affected.

What it is: CVE-2015-2209 is a medium-severity vulnerability in n/a, published on 4 Mar 2015. 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-2015-2209 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-2015-2209/ (Markdown: https://insights.sbomify.com/CVE-2015-2209/index.md)
```

## Sources

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

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