How severe is CVE-2024-52306?

CVE-2024-52306 has a CVSS score of 7.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-52306?

CVE-2024-52306 affects the following packages: backpack/filemanager (Packagist), backpack/filemanager (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2024-52306?

Update backpack/filemanager to 3.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-52306 is resolved across your whole dependency graph.

How do I detect CVE-2024-52306 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for backpack/filemanager, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-52306 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2024-52306 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-52306 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-52306?

CVE-2024-52306 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 50th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-52306?

CVE-2024-52306 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-52306 published, and has it been updated?

CVE-2024-52306 was published on November 13, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

CVE-2024-52306 — filemanager

HIGHFix: Laravel-Backpack/FileManager@2830498

CVE-2024-52306 is a high-severity (CVSS 7.6) Deserialization of Untrusted Data vulnerability in backpack/filemanager. A fix is available for backpack/filemanager — see the affected versions and patch details below.

FileManager Deserialization of Untrusted Data

Also known asGHSA-8237-957h-h2c2

Published

Nov 13, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-52306.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐘backpack/filemanager🐘backpack/filemanager

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Deserialization of untrusted data from the mimes parameter could lead to remote code execution.

Patches

Fixed in 3.0.9

Workarounds

Not needed, a composer update will solve it in a non-breaking way.

References

Reported responsibly Vladislav Gladkiy at Positive Technologies.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`backpack/filemanager`	≥ 3.0.0&&< 3.0.9	3.0.9`composer require backpack/filemanager:^3.0.9`
🐘Packagist	`backpack/filemanager`	all versions	2.0.2`composer require backpack/filemanager:^2.0.2`

Affected Products

1 product · 2 configurations

Application

filemanagerbackpackforlaravel

≥ 3.0.0 && < 3.0.9

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for backpack/filemanager, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update backpack/filemanager to 3.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-52306 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

### Impact Deserialization of untrusted data from the `mimes` parameter could lead to remote code execution. ### Patches Fixed in 3.0.9 ### Workarounds Not needed, a `composer update` will solve it in a non-breaking way. ### References Reported responsibly [Vladislav Gladkiy](https://github.com/catferq) at [Positive Technologies](https://www.ptsecurity.com/ww-en/).