Summary
baserCMS before 3.0.8 allows remote authenticated users to modify arbitrary user settings via a crafted request.
Impact
Affected versions
baserproject/basercms (<= 3.0.7)
Security releases
baserproject/basercms → 3.0.8 (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.
Remediation advice
Upgrade baserproject/basercms to 3.0.8 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2015-5640? CVE-2015-5640 is a medium-severity security vulnerability in baserproject/basercms (composer), affecting versions <= 3.0.7. It is fixed in 3.0.8.
- Which versions of baserproject/basercms are affected by CVE-2015-5640? baserproject/basercms (composer) versions <= 3.0.7 is affected.
- Is there a fix for CVE-2015-5640? Yes. CVE-2015-5640 is fixed in 3.0.8. Upgrade to this version or later.
- Is CVE-2015-5640 exploitable, and should I be worried? Whether CVE-2015-5640 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-2015-5640 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-2015-5640? Upgrade
baserproject/basercmsto 3.0.8 or later.