Which versions of melisplatform/melis-cms-slider are affected by CVE-2025-10353?

melisplatform/melis-cms-slider (composer) versions < 5.3.1 is affected.

Is there a fix for CVE-2025-10353?

Yes. CVE-2025-10353 is fixed in 5.3.1. Upgrade to this version or later.

Is CVE-2025-10353 exploitable, and should I be worried?

Whether CVE-2025-10353 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-2025-10353 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.

CVE-2025-10353 in melisplatform/melis-cms-slider

Q: What is CVE-2025-10353?

CVE-2025-10353 is a critical-severity security vulnerability in melisplatform/melis-cms-slider (composer), affecting versions < 5.3.1. It is fixed in 5.3.1.

Q: Is there a fix for CVE-2025-10353?

Yes. CVE-2025-10353 is fixed in 5.3.1. Upgrade to this version or later.

Q: Is CVE-2025-10353 exploitable, and should I be worried?

Whether CVE-2025-10353 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-2025-10353 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-2025-10353?

Upgrade melisplatform/melis-cms-slider to 5.3.1 or later.

CVE-2025-10353

CVE-2025-10353 is a critical-severity security vulnerability in melisplatform/melis-cms-slider (composer), affecting versions < 5.3.1. It is fixed in 5.3.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Melis Platform CMS Unauthenticated File Upload Leading to RCE

File upload leading to remote code execution (RCE) in the “melis-cms-slider” module of Melis Technology's Melis Platform. This vulnerability allows an attacker to upload a malicious file via a POST request to '/melis/MelisCmsSlider/MelisCmsSliderDetails/saveDetailsForm' using the 'mcsdetail_img' parameter.

Impact

Affected versions

melisplatform/melis-cms-slider (< 5.3.1)

Security releases

melisplatform/melis-cms-slider → 5.3.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

Upgrade melisplatform/melis-cms-slider to 5.3.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-10353? CVE-2025-10353 is a critical-severity security vulnerability in melisplatform/melis-cms-slider (composer), affecting versions < 5.3.1. It is fixed in 5.3.1.
Which versions of melisplatform/melis-cms-slider are affected by CVE-2025-10353? melisplatform/melis-cms-slider (composer) versions < 5.3.1 is affected.
Is there a fix for CVE-2025-10353? Yes. CVE-2025-10353 is fixed in 5.3.1. Upgrade to this version or later.
Is CVE-2025-10353 exploitable, and should I be worried? Whether CVE-2025-10353 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-2025-10353 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-2025-10353? Upgrade melisplatform/melis-cms-slider to 5.3.1 or later.