CVE-2006-3332
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 index.php in Zorum Forum 3.5 allows remote attackers to execute arbitrary SQL commands via the (1) offset, (2) tid, (3) fromid, (4) sortby, (5) fromfrommethod, and (6) fromfromlist parameters.
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 · high confidenceSQL injection vulnerability in Zorum Forum 3.5's index.php allows remote attackers to execute arbitrary SQL commands via six unsanitized GET parameters (offset, tid, fromid, sortby, fromfrommethod, fromfromlist). User-supplied input is directly concatenated into SQL queries without proper parameterization.
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= 3.0= 3.1= 3.2= 3.3= 3.4= 3.5CVSS 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 Zorum Forum installationSearch web server directories for index.php files containing 'Zorum' or 'zorum' in comments or content, typically found in /var/www/, /home/, or C:\inetpub\Affected if Zorum Forum index.php file exists on the server
-
Identify Zorum versionCheck the source code of index.php for version indicators (search for '3.0', '3.1', '3.2', '3.3', '3.4', '3.5') or check any version files, README, or config files in the Zorum directoryAffected if Installed version is 3.0, 3.1, 3.2, 3.3, 3.4, or 3.5
-
Verify vulnerable parameters are processedExamine index.php source code to confirm it handles GET parameters: offset, tid, fromid, sortby, fromfrommethod, fromfromlist. Search for direct $_GET usage of these parameter names without sanitization functionsAffected if Code shows direct use of $_GET['offset'], $_GET['tid'], $_GET['fromid'], $_GET['sortby'], $_GET['fromfrommethod'], or $_GET['fromfromlist'] without escaping or parameterized queries
-
Check for SQL query constructionSearch index.php for SQL query strings (SELECT, INSERT, UPDATE, DELETE) that concatenate the six vulnerable GET parameters directly into the queryAffected if SQL queries concatenate the GET parameters directly without using prepared statements or escaping functions
The environment is affected if Zorum Forum versions 3.0-3.5 are installed and the index.php file processes the six vulnerable GET parameters (offset, tid, fromid, sortby, fromfrommethod, fromfromlist) without sanitization in SQL queries.
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 dataReplace dynamic SQL query construction with parameterized queries (prepared statements) for all six affected parameters, or migrate to a currently supported forum platform if Zorum is no longer maintained.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-3332 — 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-2006-3332 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