What is CVE-2022-39298?

CVE-2022-39298 is a high-severity insecure deserialization vulnerability in melisplatform/melis-front (composer), affecting versions < 5.0.1. It is fixed in 5.0.1. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.

How severe is CVE-2022-39298?

CVE-2022-39298 has a CVSS score of 7.7 (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 melisplatform/melis-front are affected by CVE-2022-39298?

melisplatform/melis-front (composer) versions < 5.0.1 is affected.

Is there a fix for CVE-2022-39298?

Yes. CVE-2022-39298 is fixed in 5.0.1. Upgrade to this version or later.

Is CVE-2022-39298 exploitable, and should I be worried?

Whether CVE-2022-39298 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-2022-39298 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-2022-39298?

Upgrade melisplatform/melis-front to 5.0.1 or later.

CVE-2022-39298 in melisplatform/melis-front

Q: How severe is CVE-2022-39298?

CVE-2022-39298 has a CVSS score of 7.7 (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 melisplatform/melis-front are affected by CVE-2022-39298?

melisplatform/melis-front (composer) versions < 5.0.1 is affected.

Q: Is there a fix for CVE-2022-39298?

Yes. CVE-2022-39298 is fixed in 5.0.1. Upgrade to this version or later.

Q: Is CVE-2022-39298 exploitable, and should I be worried?

Whether CVE-2022-39298 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-2022-39298 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-2022-39298?

Upgrade melisplatform/melis-front to 5.0.1 or later.

Summary

melisplatform/melis-front vulnerable to deserialization of untrusted data

References

https://github.com/melisplatform/melis-front/commit/89ae612d5f1f7aa2fb621ee8de27dffe1feb851e

For more information

If you have any questions or comments about this advisory, you can contact:

The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;
The maintainers, by opening an issue on this repository.

Impact

Attackers can deserialize arbitrary data on affected versions of melisplatform/melis-front, and ultimately leads to the execution of arbitrary PHP code on the system. Conducting this attack does not require authentication.

Users should immediately upgrade to melisplatform/melis-front >= 5.0.1.

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-2022-39298 has a CVSS score of 7.7 (High). The vector is network-reachable, no privileges required, and no user interaction. 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 (5.0.1); upgrading removes the vulnerable code path.

Affected versions

melisplatform/melis-front (< 5.0.1)

Security releases

melisplatform/melis-front → 5.0.1 (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

This issue was addressed by restricting allowed classes when deserializing user-controlled data.

Frequently Asked Questions

What is CVE-2022-39298? CVE-2022-39298 is a high-severity insecure deserialization vulnerability in melisplatform/melis-front (composer), affecting versions < 5.0.1. It is fixed in 5.0.1. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
How severe is CVE-2022-39298? CVE-2022-39298 has a CVSS score of 7.7 (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 melisplatform/melis-front are affected by CVE-2022-39298? melisplatform/melis-front (composer) versions < 5.0.1 is affected.
Is there a fix for CVE-2022-39298? Yes. CVE-2022-39298 is fixed in 5.0.1. Upgrade to this version or later.
Is CVE-2022-39298 exploitable, and should I be worried? Whether CVE-2022-39298 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-2022-39298 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-2022-39298? Upgrade melisplatform/melis-front to 5.0.1 or later.