Dl3 Tt News AlertsApplication · TYPO3
CVE-2010-0337
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 tt_news Mail alert (dl3_tt_news_alerts) extension 0.2.0 and earlier for TYPO3 allows remote attackers to execute arbitrary SQL commands 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 · moderate confidenceSQL injection in the dl3_tt_news_alerts TYPO3 extension allows remote, unauthenticated attackers to inject arbitrary SQL commands through unspecified input vectors. The vulnerability affects version 0.2.0 and earlier of the tt_news Mail alert extension for TYPO3 CMS.
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
Dl3 Tt News AlertsApplication
<= 0.2.0CVSS 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.
-
Locate the dl3_tt_news_alerts extension directoryCheck for the presence of the extension folder in your TYPO3 installation under typo3/ext/dl3_tt_news_alerts/ or typo3/ext/tt_news_alerts/Affected if The extension directory exists in the TYPO3 extensions folder
-
Identify the installed versionOpen the ext_emconf.php file within the extension directory and read the version number from the $EM_CONF arrayAffected if The version listed is 0.2.0 or any version lower than 0.2.0
-
Verify extension is loaded in TYPO3Check your TYPO3 package states configuration (usually in var/Configuration/PackageStates.php or typo3conf/PackageStates.php) to see if the extension is marked as activeAffected if The extension appears in the PackageStates.php file with active status set to true
-
Confirm the extension handles external inputReview the extension PHP files for direct use of $_GET, $_POST, or $_REQUEST parameters in database queries without proper escaping or prepared statementsAffected if User-supplied input is used in SQL queries without parameterization
You are affected if the dl3_tt_news_alerts extension is installed, active, and running version 0.2.0 or lower in your TYPO3 environment.
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 to a patched version if available; otherwise disable the extension immediately and implement input sanitization or parameterized queries at the application layer. Consider migrating to a maintained alternative or removing the extension entirely.
Fix this in Dl3 Tt News Alerts
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0337 — 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-2010-0337 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