What is CVE-2015-10018?

CVE-2015-10018 is a critical-severity SQL injection vulnerability in dbrisinajumi/d2files (composer), affecting versions < 1.0.0. It is fixed in 1.0.0. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

How severe is CVE-2015-10018?

CVE-2015-10018 has a CVSS score of 9.8 (Critical). 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 dbrisinajumi/d2files are affected by CVE-2015-10018?

dbrisinajumi/d2files (composer) versions < 1.0.0 is affected.

Is there a fix for CVE-2015-10018?

Yes. CVE-2015-10018 is fixed in 1.0.0. Upgrade to this version or later.

Is CVE-2015-10018 exploitable, and should I be worried?

Whether CVE-2015-10018 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-2015-10018 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-2015-10018 in dbrisinajumi/d2files

Q: How severe is CVE-2015-10018?

CVE-2015-10018 has a CVSS score of 9.8 (Critical). 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 dbrisinajumi/d2files are affected by CVE-2015-10018?

dbrisinajumi/d2files (composer) versions < 1.0.0 is affected.

Q: Is there a fix for CVE-2015-10018?

Yes. CVE-2015-10018 is fixed in 1.0.0. Upgrade to this version or later.

Q: Is CVE-2015-10018 exploitable, and should I be worried?

Whether CVE-2015-10018 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-2015-10018 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-2015-10018?

Upgrade dbrisinajumi/d2files to 1.0.0 or later.

Summary

DBRisinajumi d2files SQL Injection vulnerability

A vulnerability has been found in DBRisinajumi d2files and classified as critical. Affected by this vulnerability is the function actionUpload/actionDownloadFile of the file controllers/D2filesController.php. The manipulation leads to sql injection. Upgrading to version 1.0.0 can address this issue. The name of the patch is b5767f2ec9d0f3cbfda7f13c84740e2179c90574. It is recommended to upgrade the affected component. The identifier VDB-217561 was assigned to this vulnerability.

Impact

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2015-10018 has a CVSS score of 9.8 (Critical). 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 (1.0.0); upgrading removes the vulnerable code path.

Affected versions

dbrisinajumi/d2files (< 1.0.0)

Security releases

dbrisinajumi/d2files → 1.0.0 (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 dbrisinajumi/d2files to 1.0.0 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-2015-10018? CVE-2015-10018 is a critical-severity SQL injection vulnerability in dbrisinajumi/d2files (composer), affecting versions < 1.0.0. It is fixed in 1.0.0. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
How severe is CVE-2015-10018? CVE-2015-10018 has a CVSS score of 9.8 (Critical). 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 dbrisinajumi/d2files are affected by CVE-2015-10018? dbrisinajumi/d2files (composer) versions < 1.0.0 is affected.
Is there a fix for CVE-2015-10018? Yes. CVE-2015-10018 is fixed in 1.0.0. Upgrade to this version or later.
Is CVE-2015-10018 exploitable, and should I be worried? Whether CVE-2015-10018 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-10018 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-10018? Upgrade dbrisinajumi/d2files to 1.0.0 or later.