# CVE-2018-19458: Unauthenticated File Read in PHP Proxy

> Unauthenticated attackers can read arbitrary server files via a Local File Inclusion vulnerability in PHP Proxy.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 22 Nov 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-3x3m-p2wx-g7cw

## What is CVE-2018-19458?

CVE-2018-19458 is a high-severity path traversal vulnerability in n/a, published on 22 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In PHP Proxy 3.0.3, any user can read files from the server without authentication due to an index.php?q=file:/// LFI URI, a different vulnerability than CVE-2018-19246.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-19458?

2 open source packages ship an affected version, including athlon1600/php-proxy-app. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `athlon1600/php-proxy-app` | Packagist | All versions to 3.0 | None |
| `athlon1600/php-proxy-app` | Packagist | All versions to 3.0 | None |

Products: Php-Proxy Php-Proxy.

## How do I fix CVE-2018-19458?

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

## Is CVE-2018-19458 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-19458 exists.

Public exploit code:

- PHP Proxy 3.0.3 - Local File Inclusion (exploitdb)
- PHP Proxy 3.0.3 - Local File Inclusion (nuclei): http/cves/2018/CVE-2018-19458.yaml

## Other vulnerabilities in n/a

- [CVE-2018-19784](https://insights.sbomify.com/CVE-2018-19784/): Weak Cryptography in PHP-Proxy (high 7.5)
- [CVE-2018-19246](https://insights.sbomify.com/CVE-2018-19246/): LFI in PHP-Proxy 5.1.0 (high 7.5)
- [CVE-2018-19785](https://insights.sbomify.com/CVE-2018-19785/): XSS in PHP-Proxy-App through v3.0 (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19458 and fix it if it is affected.

What it is: CVE-2018-19458 is a high-severity path traversal vulnerability in n/a, published on 22 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-19458 exists.

Affected packages and fixed versions:
- athlon1600/php-proxy-app (Packagist): affected all versions up to 3.0; no fix listed
- athlon1600/php-proxy-app (Packagist): affected all versions up to 3.0; no fix listed

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

## Sources

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

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