CVE-2006-3329
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 search.php in PHP/MySQL Classifieds (PHP Classifieds) allows remote attackers to execute arbitrary SQL commands via the rate parameter.
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 the search.php file of PHP/MySQL Classifieds allows remote attackers to inject arbitrary SQL commands through the 'rate' parameter. The application fails to properly sanitize user input before using it in SQL queries, enabling attackers to manipulate 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= 6.04CVSS 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 Deltascripts Php Classifieds is installedSearch the webroot for files containing 'Deltascripts' or 'Php Classifieds' branding, or check for a file named index.php with Deltascripts referencesAffected if The application is Deltascripts Php Classifieds
-
Verify the installed versionLook for a version identifier in the source code, a version file, or the admin panel. Check the main index.php or a separate version/info file for the version numberAffected if The version is 6.04 exactly
-
Locate the search.php fileFind search.php within the application directory structure - it is typically in the root or a includes folder of the classifieds installationAffected if search.php exists in the application
-
Check if the rate parameter is present and unsanitizedOpen search.php and examine how the 'rate' parameter is handled - look for direct use in SQL queries without escaping, parametrization, or validation functionsAffected if The code directly uses $_GET['rate'] or $_POST['rate'] in a SQL query without sanitization functions like mysql_real_escape_string, parameterized queries, or input validation
-
Confirm the database is MySQLCheck the application configuration file (often config.php or db.php) to confirm MySQL is being used as the database backendAffected if MySQL is the active database backend
You are affected if you have Deltascripts Php Classifieds version 6.04 with the search.php file present and the 'rate' parameter used in unsanitized 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 dataFix by implementing parameterized queries (prepared statements) for all database queries using the 'rate' parameter, or at minimum apply strict input validation/sanitization. Review other parameters in search.php and throughout the application for similar injection flaws.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-3329 — 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-3329 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