# CVE-2014-5094: Information disclosure in n/a

> Remote attackers can obtain sensitive configuration information by accessing the phpinfo action in Status2k.

- **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:** 20 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7vpq-c2mw-x963

## What is CVE-2014-5094?

CVE-2014-5094 is a medium-severity vulnerability in n/a, published on 20 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Status2k allows remote attackers to obtain configuration information via a phpinfo action in a request to status/index.php, which calls the phpinfo function.

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

## Which versions are affected by CVE-2014-5094?

It affects 1 product.


Products: Status2k Status2k.

## How do I fix CVE-2014-5094?

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

## Is CVE-2014-5094 being exploited?

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

Public exploit code:

- Status2k Server Monitoring Software - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-5091](https://insights.sbomify.com/CVE-2014-5091/): Code injection in n/a (critical 9.8)
- [CVE-2014-5093](https://insights.sbomify.com/CVE-2014-5093/): Missing authorization in n/a (critical 9.8)
- [CVE-2014-5092](https://insights.sbomify.com/CVE-2014-5092/): Command injection in n/a (high 8.8)
- [CVE-2014-5089](https://insights.sbomify.com/CVE-2014-5089/): SQL injection in n/a (high 7.5)
- [CVE-2014-5090](https://insights.sbomify.com/CVE-2014-5090/): Command injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-5094 and fix it if it is affected.

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

## Sources

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

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