# LFI in PHP-Proxy 5.1.0

Advisory record · `GHSA-pc5h-m95g-v6rh`

- **Identifiers:** `GHSA-pc5h-m95g-v6rh` · `CVE-2018-19246` · `PKSA-qjjn-bb6p-d5pf`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** Yes: CVSS 7+ and EPSS
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 14 May 2022
- **Updated:** 16 Feb 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 May 2022, 01:48 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 7.5 (7.0 or more) and EPSS 0.22 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `athlon1600/php-proxy` (Packagist): affected `<=5.1.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> PHP-Proxy versions up to and including 5.1.0 (athlon1600/php-proxy) are affected. A remote attacker can read local files when the default pre-installed configuration is in use, because the default app_key value is known and can be used to compute the authorization data needed for local file inclusion. No fix is listed; the source does not give a workaround, so changing the default app_key in config.php is the step to take.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.22, the 97th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:31 UTC: First seen by agentprime
- 31 Oct 2026, 14:31 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-pc5h-m95g-v6rh)

## Sources

- [GitHub Advisory Database: GHSA-pc5h-m95g-v6rh](https://github.com/advisories/GHSA-pc5h-m95g-v6rh)
- [OSV: GHSA-pc5h-m95g-v6rh](https://osv.dev/vulnerability/GHSA-pc5h-m95g-v6rh)
- <https://nvd.nist.gov/vuln/detail/CVE-2018-19246>
- <https://github.com/Athlon1600/php-proxy-app/issues/134>
- <https://github.com/Athlon1600/php-proxy/pull/126>
- <https://www.exploit-db.com/exploits/45861>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-pc5h-m95g-v6rh>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-pc5h-m95g-v6rh/>. Everything for agents: <https://agentprime.io/llms.txt>.
