What is CVE-2014-3947?

CVE-2014-3947 is a high-severity code injection vulnerability in in2code/powermail (composer), affecting versions < 1.6.11. It is fixed in 1.6.11, 2.0.14. Untrusted input is evaluated as executable code within the application's runtime environment.

Which versions of in2code/powermail are affected by CVE-2014-3947?

in2code/powermail (composer) versions < 1.6.11 is affected.

Is there a fix for CVE-2014-3947?

Yes. CVE-2014-3947 is fixed in 1.6.11, 2.0.14. Upgrade to this version or later.

Is CVE-2014-3947 exploitable, and should I be worried?

Whether CVE-2014-3947 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-2014-3947 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-2014-3947 in in2code/powermail

Q: Which versions of in2code/powermail are affected by CVE-2014-3947?

in2code/powermail (composer) versions < 1.6.11 is affected.

Q: Is there a fix for CVE-2014-3947?

Yes. CVE-2014-3947 is fixed in 1.6.11, 2.0.14. Upgrade to this version or later.

Q: Is CVE-2014-3947 exploitable, and should I be worried?

Whether CVE-2014-3947 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-2014-3947 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-2014-3947?

Upgrade: in2code/powermail to 1.6.11 or later, in2code/powermail to 2.0.14 or later.

Summary

TYPO3 powermail extension has unrestricted file upload vulnerability

Unrestricted file upload vulnerability in the powermail extension before 1.6.11 and 2.x before 2.0.14 for TYPO3 allows remote attackers to execute arbitrary code by uploading a file with a crafted extension, then accessing it via unspecified vectors.

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.

Affected versions

in2code/powermail (< 1.6.11) in2code/powermail (>= 2.0.0, < 2.0.14)

Security releases

in2code/powermail → 1.6.11 (composer) in2code/powermail → 2.0.14 (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 the following packages to resolve this vulnerability:

in2code/powermail to 1.6.11 or later; in2code/powermail to 2.0.14 or later

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

Frequently Asked Questions

What is CVE-2014-3947? CVE-2014-3947 is a high-severity code injection vulnerability in in2code/powermail (composer), affecting versions < 1.6.11. It is fixed in 1.6.11, 2.0.14. Untrusted input is evaluated as executable code within the application's runtime environment.
Which versions of in2code/powermail are affected by CVE-2014-3947? in2code/powermail (composer) versions < 1.6.11 is affected.
Is there a fix for CVE-2014-3947? Yes. CVE-2014-3947 is fixed in 1.6.11, 2.0.14. Upgrade to this version or later.
Is CVE-2014-3947 exploitable, and should I be worried? Whether CVE-2014-3947 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-2014-3947 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-2014-3947?
- Upgrade in2code/powermail to 1.6.11 or later
- Upgrade in2code/powermail to 2.0.14 or later

Other vulnerabilities in in2code/powermail

CVE-IDSeverityPackage summary

CVE-2025-7899Mediumin2code/powermail: Powermail extension for TYPO3 allows Insecure Direct Object Reference CVE-2024-47047Mediumin2code/powermail: powermail TYPO3 extension has Insecure Direct Object Reference CVE-2024-45232Mediumin2code/powermail: "powermail" (powermail) Insecure Direct Object Reference (IDOR)CVE-2024-45233Mediumin2code/powermail: Powermail TYPO3 extension Broken Access Control in the OutputController CVE-2010-3604Highin2code/powermail: powermail extension for TYPO3 vulnerable to SQL Injection