StatisticsTYPO3 extension · Kennziffer
CVE-2014-6293
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 · uneditedSQL injection vulnerability in the Statistics (ke_stats) extension before 1.1.2 for TYPO3 allows remote attackers to execute arbitrary SQL commands via unspecified vectors, as exploited in the wild in February 2014.
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 · moderate confidenceSQL injection vulnerability in the ke_stats TYPO3 extension versions prior to 1.1.2 allows remote attackers to execute arbitrary SQL commands. The vulnerability was actively exploited in the wild in February 2014.
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
StatisticsTYPO3 extension
<= 1.1.1CVSS 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.
-
Verify ke_stats extension installation statusIn TYPO3 backend, navigate to Extension Manager > Manage Extensions and search for 'ke_stats' or 'kennziffer_statistics'. Alternatively, check if the directory typo3conf/ext/ke_stats/ exists on the server filesystem.Affected if The ke_stats directory exists in typo3conf/ext/ or the extension appears as installed in the TYPO3 Extension Manager
-
Check installed ke_stats versionOpen the file typo3conf/ext/ke_stats/ext_emconf.php and locate the 'version' field in the $EM_CONF array. Alternatively, in TYPO3 backend Extension Manager, click on the ke_stats extension details to view the installed version number.Affected if The reported version number is 1.1.1 or lower (any version prior to 1.1.2)
-
Confirm extension is loaded and activeCheck typo3conf/localconf.php or typo3conf/LocalConfiguration.php for 'ke_stats' in the 'TYPO3_CONF_VARS' > 'EXT' > 'extList' array. In TYPO3 4.x, also check typo3conf/localconf.php for $TYPO3_CONF_VARS['EXT']['extList'].Affected if The extension is listed in the active extension list (extList) and the site is running
-
Identify accessible entry pointsReview the extension's main PHP files in typo3conf/ext/ke_stats/ (such as pi1/class.tx_ke_stats_pi1.php or similar controller files) for parameters passed to database queries without proper sanitization. The vulnerability exists in how user input is handled in SQL queries.Affected if The extension code processes GET/POST parameters directly into SQL queries without prepared statements or escaping
If the ke_stats TYPO3 extension is installed and its version is 1.1.1 or lower (check via ext_emconf.php), the environment is affected by this SQL injection vulnerability.
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 ke_stats extension to version 1.1.2 or later. If unable to upgrade immediately, consider disabling the extension until patching can be completed.
Fix this in Statistics
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6293 — 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-6293 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