# czim/file-handling vulnerable to SSRF and directory traversal

Advisory record · `GHSA-6rgh-r6j3-3223`

- **Identifiers:** `GHSA-6rgh-r6j3-3223` · `CVE-2024-47049` · `PKSA-tmwg-zdtv-1ff9`
- **State:** Confirmed
- **Severity:** CVSS 8.2 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 17 Sept 2024
- **Updated:** 19 Mar 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 Sept 2024, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `czim/file-handling` (Packagist): affected `<1.5.0 || >=2.0.0, <2.3.0`; fixed in `1.5.0`, `2.3.0`

## Machine-written summary

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

> The czim/file-handling Composer package is vulnerable in versions before 1.5.0 and from 2.0.0 before 2.3.0. Its makeFromUrl and makeFromAny functions do not properly validate URLs, so an attacker who can supply a URL can cause server-side requests (SSRF) and read local files through directory traversal. Upgrade to version 1.5.0 or 2.3.0.

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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0064, the 51st percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:27 UTC: First seen by agentprime
- 31 Oct 2026, 14:27 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6rgh-r6j3-3223)

## Sources

- [GitHub Advisory Database: GHSA-6rgh-r6j3-3223](https://github.com/advisories/GHSA-6rgh-r6j3-3223)
- [OSV: GHSA-6rgh-r6j3-3223](https://osv.dev/vulnerability/GHSA-6rgh-r6j3-3223)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-47049>
- <https://github.com/czim/file-handling/commit/95dfda850536bf35e684619598b9d02f4c97680d>
- <https://github.com/czim/file-handling/commit/dcf879896efe3457f51af9c8eab9f70dfc709a99>
- <https://github.com/czim/file-handling>
- <https://github.com/czim/file-handling/blob/2.3.0/SECURITY.md>

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-6rgh-r6j3-3223>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6rgh-r6j3-3223/>. Everything for agents: <https://agentprime.io/llms.txt>.
