Zak Store ManagementApplication · TYPO3
CVE-2010-0344
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 zak_store_management extension 1.0.0 and earlier 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 zak_store_management TYPO3 extension (versions 1.0.0 and earlier) allows remote unauthenticated attackers to execute arbitrary SQL commands via unspecified input vectors. The vulnerability stems from improper sanitization of user-supplied data in SQL queries, enabling attackers to manipulate query logic.
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
Zak Store ManagementApplication
<= 1.0.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.
-
Identify if zak_store_management extension is installedCheck TYPO3 extension manager/list for zak_store_management, or search for the extension directory in typo3conf/ext/ for a folder named 'zak_store_management'Affected if The extension directory exists in the TYPO3 installation
-
Verify the extension versionCheck the extension's ext_emconf.php file located in typo3conf/ext/zak_store_management/ and look for the 'version' key in the $EM_CONF arrayAffected if The version is 1.0.0 or earlier, or if the version key is missing entirely (indicating an old/unmaintained release)
-
Confirm the extension is enabledCheck TYPO3's system extension configuration or the ext_localconf.php file to confirm the extension is loaded and active in the TYPO3 instanceAffected if The extension is installed and listed as active in TYPO3 extension manager
-
Check for exposure to web requestsInspect the extension's PHP files (particularly any controller, repository or model classes) for direct use of $_GET, $_POST, or $_REQUEST parameters in SQL query strings without proper sanitizationAffected if User-supplied input parameters are used in database queries without prepared statements or escaping functions
A user is affected if the zak_store_management extension version 1.0.0 or earlier is installed, enabled, and accessible via web requests in a 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 dataUpdate the zak_store_management extension to the latest patched version; if no patch exists, remove the extension entirely. Alternatively, apply input validation/sanitization fixes to all database query paths in the extension code.
Fix this in Zak Store Management
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-0344 — 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-0344 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