# Code Injection in froxlor/froxlor

Advisory record · `GHSA-vp4r-h765-5mwp`

- **Identifiers:** `GHSA-vp4r-h765-5mwp` · `CVE-2023-0877` · `PKSA-y2p5-gr81-xyk9`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-94](https://cwe.mitre.org/data/definitions/94.html)
- **Tags:** [Code injection](https://agentprime.io/advisories/tag/code-injection.md)
- **Published:** 17 Feb 2023
- **Updated:** 8 Nov 2023
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 Feb 2023, 03:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

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

## Affected packages

- `froxlor/froxlor` (Packagist): affected `<2.0.11`; fixed in `2.0.11`

## Machine-written summary

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

> Froxlor/froxlor versions prior to 2.0.11 contain a code injection vulnerability. The source gives few details about how it can be triggered or what access an attacker needs. Upgrade to froxlor/froxlor 2.0.11 or later.

Written 5 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

- 9.1 Critical, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`, from CNA (@huntrdev)

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

## Timeline

- 31 Oct 2026, 14:32 UTC: First seen by agentprime
- 31 Oct 2026, 14:32 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vp4r-h765-5mwp)

## Sources

- [GitHub Advisory Database: GHSA-vp4r-h765-5mwp](https://github.com/advisories/GHSA-vp4r-h765-5mwp)
- [OSV: GHSA-vp4r-h765-5mwp](https://osv.dev/vulnerability/GHSA-vp4r-h765-5mwp)
- <https://nvd.nist.gov/vuln/detail/CVE-2023-0877>
- <https://github.com/froxlor/froxlor/commit/aa48ffca2bcaf7ae57be3b8147bb3138abdab984>
- <https://github.com/Froxlor/Froxlor>
- <https://huntr.dev/bounties/b29cf038-06f1-4fb0-9437-08f2991f92a8>

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-vp4r-h765-5mwp>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vp4r-h765-5mwp/>. Everything for agents: <https://agentprime.io/llms.txt>.
