CVE-2024-47049
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe czim/file-handling package before 1.5.0 and 2.x before 2.3.0 (used with PHP Composer) does not properly validate URLs within makeFromUrl and makeFromAny, leading to SSRF, and to directory traversal for the reading of local files.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe czim/file-handling PHP Composer package before versions 1.5.0 and 2.3.0 contains improper URL validation in the makeFromUrl and makeFromAny methods, enabling Server-Side Request Forgery (SSRF) attacks and directory traversal for unauthorized local file access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.5.0>= 2.0.0, < 2.3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed package versionRun `composer show czim/file-handling` in your project root to display the currently installed version of the packageAffected if The version displayed is below 1.5.0 or is 2.x.x and below 2.3.0 (e.g., 2.0.0, 2.1.0, 2.2.0)
-
Locate method usage in codebaseSearch your codebase for calls to `makeFromUrl` and `makeFromAny` methods, typically in files that use the czim/file-handling package (e.g., grep -r 'makeFromUrl\|makeFromAny' your source directories)Affected if These methods are called with user-controlled URLs or file paths without additional validation
-
Identify URL input sourceTrace the data flow into makeFromUrl and makeFromAny calls to determine if input originates from user request parameters, API calls, or external sourcesAffected if User-supplied or untrusted data is passed directly to these methods without sanitization
-
Check for URL validation wrapperInspect any validation or filtering logic surrounding the method calls to see if external URL validation is implemented before passing to makeFromUrl or makeFromAnyAffected if No validation wrapper exists and the application accepts arbitrary URLs or file paths
You are affected if the installed czim/file-handling version is below 1.5.0 or between 2.0.0 and 2.3.0, AND your application uses makeFromUrl or makeFromAny with untrusted input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.5.02.3.0
Upgrade the czim/file-handling package to version 1.5.0 or 2.3.0 or later via Composer to obtain patched validation logic.
czim/file-handling:^1.5.0 for 1.x users, or czim/file-handling:^2.3.0 for 2.x users
- Run `composer require czim/file-handling:^1.5.0` if using version 1.x, or `composer require czim/file-handling:^2.3.0` if using version 2.x
- Run `composer update czim/file-handling` to install the fixed version
- Verify the installed version with `composer show czim/file-handling` to confirm the patch was applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47049 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data