What is CVE-2015-10009?

CVE-2015-10009 is a critical-severity code injection vulnerability in nonfiction/nterchange (composer), affecting versions < 4.1.1. It is fixed in 4.1.1. Untrusted input is evaluated as executable code within the application's runtime environment.

How severe is CVE-2015-10009?

CVE-2015-10009 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 nonfiction/nterchange are affected by CVE-2015-10009?

nonfiction/nterchange (composer) versions < 4.1.1 is affected.

Is there a fix for CVE-2015-10009?

Yes. CVE-2015-10009 is fixed in 4.1.1. Upgrade to this version or later.

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

Whether CVE-2015-10009 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-10009 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-10009 in nonfiction/nterchange

Q: How severe is CVE-2015-10009?

CVE-2015-10009 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 nonfiction/nterchange are affected by CVE-2015-10009?

nonfiction/nterchange (composer) versions < 4.1.1 is affected.

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

Yes. CVE-2015-10009 is fixed in 4.1.1. Upgrade to this version or later.

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

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

Upgrade nonfiction/nterchange to 4.1.1 or later.

Summary

nterchange Code Injection vulnerability

A vulnerability was found in nterchange up to 4.1.0. It has been rated as critical. This issue affects the function getContent of the file app/controllers/code_caller_controller.php. The manipulation of the argument q with the input %5C%27%29;phpinfo%28%29;/* leads to code injection. The exploit has been disclosed to the public and may be used. Upgrading to version 4.1.1 is able to address this issue. The name of the patch is fba7d89176fba8fe289edd58835fe45080797d99. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-217187.

Impact

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2015-10009 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 (4.1.1); upgrading removes the vulnerable code path.

Affected versions

nonfiction/nterchange (< 4.1.1)

Security releases

nonfiction/nterchange → 4.1.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 nonfiction/nterchange to 4.1.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-2015-10009? CVE-2015-10009 is a critical-severity code injection vulnerability in nonfiction/nterchange (composer), affecting versions < 4.1.1. It is fixed in 4.1.1. Untrusted input is evaluated as executable code within the application's runtime environment.
How severe is CVE-2015-10009? CVE-2015-10009 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 nonfiction/nterchange are affected by CVE-2015-10009? nonfiction/nterchange (composer) versions < 4.1.1 is affected.
Is there a fix for CVE-2015-10009? Yes. CVE-2015-10009 is fixed in 4.1.1. Upgrade to this version or later.
Is CVE-2015-10009 exploitable, and should I be worried? Whether CVE-2015-10009 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-10009 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-10009? Upgrade nonfiction/nterchange to 4.1.1 or later.