What is CVE-2024-52306?

CVE-2024-52306 is a high-severity insecure deserialization vulnerability in backpack/filemanager (composer), affecting versions >= 3.0.0, < 3.0.9. It is fixed in 3.0.9, 2.0.2. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.

How severe is CVE-2024-52306?

CVE-2024-52306 has a CVSS score of 7.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of backpack/filemanager are affected by CVE-2024-52306?

backpack/filemanager (composer) versions >= 3.0.0, < 3.0.9 is affected.

Is there a fix for CVE-2024-52306?

Yes. CVE-2024-52306 is fixed in 3.0.9, 2.0.2. Upgrade to this version or later.

Is CVE-2024-52306 exploitable, and should I be worried?

Whether CVE-2024-52306 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-52306 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-52306?

Upgrade: backpack/filemanager to 3.0.9 or later, backpack/filemanager to 2.0.2 or later.

CVE-2024-52306 in backpack/filemanager

Q: How severe is CVE-2024-52306?

CVE-2024-52306 has a CVSS score of 7.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of backpack/filemanager are affected by CVE-2024-52306?

backpack/filemanager (composer) versions >= 3.0.0, < 3.0.9 is affected.

Q: Is there a fix for CVE-2024-52306?

Yes. CVE-2024-52306 is fixed in 3.0.9, 2.0.2. Upgrade to this version or later.

Q: Is CVE-2024-52306 exploitable, and should I be worried?

Whether CVE-2024-52306 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-52306 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-52306?

Upgrade: backpack/filemanager to 3.0.9 or later, backpack/filemanager to 2.0.2 or later.

Summary

FileManager Deserialization of Untrusted Data vulnerability

Workarounds

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

References

Reported responsibly Vladislav Gladkiy at Positive Technologies.

Impact

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

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2024-52306 has a CVSS score of 7.6 (High). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.0.9, 2.0.2); upgrading removes the vulnerable code path.

Affected versions

backpack/filemanager (>= 3.0.0, < 3.0.9) backpack/filemanager (< 2.0.2)

Security releases

backpack/filemanager → 3.0.9 (composer) backpack/filemanager → 2.0.2 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Fixed in 3.0.9

Frequently Asked Questions

What is CVE-2024-52306? CVE-2024-52306 is a high-severity insecure deserialization vulnerability in backpack/filemanager (composer), affecting versions >= 3.0.0, < 3.0.9. It is fixed in 3.0.9, 2.0.2. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
How severe is CVE-2024-52306? CVE-2024-52306 has a CVSS score of 7.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of backpack/filemanager are affected by CVE-2024-52306? backpack/filemanager (composer) versions >= 3.0.0, < 3.0.9 is affected.
Is there a fix for CVE-2024-52306? Yes. CVE-2024-52306 is fixed in 3.0.9, 2.0.2. Upgrade to this version or later.
Is CVE-2024-52306 exploitable, and should I be worried? Whether CVE-2024-52306 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-52306 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-52306?
- Upgrade backpack/filemanager to 3.0.9 or later
- Upgrade backpack/filemanager to 2.0.2 or later