MjseventproApplication · TYPO3
CVE-2010-0340
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 MJS Event Pro (mjseventpro) extension 0.2.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 MJS Event Pro TYPO3 extension (mjseventpro) versions 0.2.1 and earlier allows remote attackers to execute arbitrary SQL commands through unsanitized input being passed to database queries.
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
MjseventproApplication
<= 0.2.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.
-
Check if Mjseventpro extension directory existsNavigate to your TYPO3 installation root and list the contents of typo3conf/ext/ to see if a directory named 'mjseventpro' is presentAffected if The extension directory typo3conf/ext/mjseventpro/ exists
-
Determine the installed version of mjseventproOpen the file typo3conf/ext/mjseventpro/ext_emconf.php and locate the 'version' field in the $EM_CONF arrayAffected if The version number retrieved is 0.2.1 or lower
-
Verify the extension is loaded and activeCheck your TYPO3 backend under Admin Tools > Extensions > Extensions (or check typo3conf/localconf.php for the extension in the $TYPO3_CONF_VARS['EXT']['extList'] array)Affected if The mjseventpro extension appears in the list of loaded/active extensions
-
Inspect extension for unsanitized database queriesReview PHP files in the mjseventpro extension directory, particularly in classes or controllers, for direct use of $_GET, $_POST, or $_REQUEST variables in SQL queries without escaping or prepared statementsAffected if PHP code in the extension uses user-supplied input directly in SQL queries without using $GLOBALS['TYPO3_DB']->fullQuoteStr or prepared statements
You are affected if the mjseventpro extension is installed, loaded, and its version is 0.2.1 or lower, as this version contains the SQL injection vulnerability in its database query handling.
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 dataUpdate to a patched version of the mjseventpro extension if available, or implement input validation/parameterized queries in the extension code to neutralize SQL injection vectors.
Fix this in Mjseventpro
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0340 — 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-0340 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