PowermailTYPO3 extension · Alex Kellner
CVE-2014-3947
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnrestricted 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe powermail TYPO3 extension before versions 1.6.11 and 2.0.14 contains an unrestricted file upload vulnerability. Attackers can upload files with crafted extensions (e.g., PHP files disguised with other extensions) and execute arbitrary code by accessing those files through unspecified vectors, likely via direct URL access to the upload directory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
PowermailTYPO3 extension
<= 1.6.10= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.7= 2.0.8= 2.0.9= 2.0.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm powermail extension is installedLog into the TYPO3 backend and navigate to the Extension Manager. Search for 'powermail' in the installed extensions list. Alternatively, check for the extension directory in typo3conf/ext/ or typo3/sysext/ if you have filesystem access.Affected if powermail appears in the list of installed extensions
-
Identify the installed powermail versionIn the Extension Manager, click on the powermail extension to view its details. The version number is displayed on the extension information page. Compare this version against the affected ranges: versions 1.6.10 and below, or versions 2.0.0 through 2.0.10.Affected if The installed version is 1.6.10 or lower, OR any version from 2.0.0 through 2.0.10
-
Verify file upload is enabled in powermailIn the TYPO3 backend, go to the Powermail plugin configuration. Check the plugin or flexform settings for any file upload related fields (often labeled as 'Upload' or 'File upload enabled'). Verify if this feature is turned on in the form creation settings.Affected if File upload functionality is enabled in any powermail form configuration
-
Locate the upload directory and verify web accessibilityCheck the powermail extension configuration for the upload path (commonly uploads/tx_powermail/ or similar under the web root). Verify that this directory exists and is accessible via HTTP. If you have server access, check for .htaccess restrictions in that directory.Affected if The upload directory exists within the web root and is accessible via direct URL without execution restrictions
You are affected if the powermail extension is installed with a version between 1.6.10 and below or between 2.0.0 and 2.0.10, file upload is enabled, and the upload directory is web-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade powermail to version 1.6.11 or 2.0.14 or later. Additionally, configure the web server to prevent execution of uploaded files (e.g., via .htaccess rules or moving uploads outside webroot).
Fix this in Powermail
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-3947 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data