CVE-2006-3330
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 · uneditedCross-site scripting (XSS) vulnerability in AddAsset1.php in PHP/MySQL Classifieds (PHP Classifieds) allows remote attackers to execute arbitrary SQL commands via the (1) ProductName ("Title" field), (2) url, and (3) Description parameters, possibly related to issues in add1.php.
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 AddAsset1.php of PHP/MySQL Classifieds allows remote attackers to inject arbitrary SQL commands via the ProductName, url, and Description parameters. Although the CVE title mentions XSS, the description clearly indicates SQL injection (arbitrary SQL command execution). The vulnerability stems from unsanitized user input being directly used in SQL 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Confirm Deltascripts Php Classifieds installationSearch the web server for files or directories containing 'deltascripts', 'classifieds', or review web application source code for branding strings referencing this productAffected if The application is not Deltascripts Php Classifieds, the check does not apply
-
Identify the installed versionCheck for version information in the application source code, such as in an about page, configuration file, header/footer includes, or a version.php file. Compare against 6.04Affected if The installed version is not 6.04, the vulnerability may not be present
-
Locate AddAsset1.php fileSearch the web root directory for the file AddAsset1.php or add1.php, which contains the vulnerable codeAffected if The file AddAsset1.php does not exist in the application, the vulnerability is not present
-
Verify web exposure of vulnerable scriptDetermine if AddAsset1.php is accessible via HTTP/HTTPS from the web. Check web server configuration and routing for direct access to this scriptAffected if AddAsset1.php is not accessible via web requests, the exploit cannot be triggered remotely
-
Check if ProductName/url/Description parameters are acceptedReview the AddAsset1.php source code to confirm it accepts and processes ProductName, url, and Description parameters in POST or GET requestsAffected if These specific parameters are not used by the script, the specific SQL injection vectors do not exist
A user is affected if they run Deltascripts Php Classifieds version 6.04 with the AddAsset1.php file accessible via the web and the application accepts ProductName, url, or Description parameters in SQL queries without sanitization.
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 dataImplement parameterized queries (prepared statements) for all SQL operations in AddAsset1.php and related files (add1.php) to prevent SQL injection. Apply proper input validation and escaping for the ProductName, url, and Description parameters.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-3330 — 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-3330 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