Vm19 UserlinksApplication · TYPO3
CVE-2010-0339
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 User Links (vm19_userlinks) extension 0.1.1 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 vulnerability in the vm19_userlinks TYPO3 extension (versions 0.1.1 and earlier) allows remote attackers to execute arbitrary SQL commands through unsanitized user input. The vulnerability has a CVSS score of 7.5 (HIGH), indicating significant risk to confidentiality and integrity.
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
Vm19 UserlinksApplication
<= 0.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 if vm19_userlinks extension is installedAccess TYPO3 backend > Extension Manager and search for 'vm19_userlinks' or list all installed extensions and look for this extensionAffected if vm19_userlinks appears in the list of installed extensions
-
Check the installed version of vm19_userlinksIn Extension Manager, click on vm19_userlinks to view its details; version is shown in the extension info panel. Alternatively, check the file typo3conf/ext/vm19_userlinks/ext_emconf.php for the 'version' fieldAffected if Version is 0.1.1 or lower
-
Confirm the extension is enabledIn Extension Manager, verify the extension status shows as 'Installed and loaded' or check if the extension is active in typo3conf/localconf.php (look for $TYPO3_CONF_VARS['EXT']['extList'] or similar)Affected if Extension is loaded and active in the TYPO3 system
-
Identify if the vulnerable user input feature is in useCheck if the extension's frontend plugins are included on any page; review page TSconfig or template includes for 'userlinks' plugin references (tx_vm19userlinks_pi1)Affected if The extension's frontend functionality is actively used on the website
You are affected if vm19_userlinks extension version 0.1.1 or lower is installed and active in your TYPO3 instance.
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 of the extension if available; otherwise, remove the extension from the TYPO3 installation. If continued use is required, implement proper input validation and parameterized queries in the extension code.
Fix this in Vm19 Userlinks
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0339 — 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-0339 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