dbcve.org
Classified AdsApplication · Pozscripts

CVE-2008-3672

HIGH · 7.5 CVSS v2.0 Published 2008-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
SQL injection vulnerability in showcategory.php in PozScripts Classified Ads allows remote attackers to execute arbitrary SQL commands via the cid parameter, a different vector than CVE-2008-3673. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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 confidence

SQL injection vulnerability in showcategory.php of PozScripts Classified Ads allows remote attackers to execute arbitrary SQL commands via the unsanitized cid parameter. The application fails to properly validate or sanitize user input before using it in SQL queries, enabling attackers to manipulate query logic and potentially access, modify, or delete database contents.

MitigationFix by implementing parameterized queries (prepared statements) for all database operations involving the cid parameter, adding proper input validation, and conducting a broader code review to identify similar injection points in the application.

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
Classified AdsApplication
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the application installation
    Search the web server document root for directories named 'classifieds', 'classified_ads', or 'pozscripts'. Common paths include /var/www/html/classifieds, /home/user/public_html/classifieds, or C:\inetpub\wwwroot\classifieds
    Affected if The PozScripts Classified Ads application is found installed on the server
  2. Verify the vulnerable file exists
    Look for showcategory.php within the application directory. Typical locations: /classifieds/showcategory.php, /classifieds/admin/showcategory.php, or /classifieds/include/showcategory.php
    Affected if The showcategory.php file exists in the application installation
  3. Confirm the application is exposed via web
    Check if the application's web directory is accessible over HTTP/HTTPS. Attempt to access the main classifieds page (e.g., http://yourdomain/classifieds/ or the specific subdirectory where it is installed)
    Affected if The application is accessible via a web browser and responding to requests
  4. Check database connectivity configuration
    Examine the application configuration files (often named config.php, settings.php, or db.php within the application root or includes folder) to confirm the application connects to a MySQL or MySQLi database
    Affected if The application is configured to use a MySQL database, which is required for the SQL injection to be exploitable
  5. Identify the cid parameter usage
    Review showcategory.php source code and look for SQL queries that incorporate the 'cid' parameter without proper sanitization. Search for patterns like $_GET['cid'] or $_REQUEST['cid'] used directly in queries
    Affected if The code shows the cid parameter being used in SQL queries without parameterized queries, prepared statements, or input sanitization

If PozScripts Classified Ads is installed and showcategory.php exists with the cid parameter being used in unsanitized SQL queries, the environment is affected by CVE-2008-3672.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Fix by implementing parameterized queries (prepared statements) for all database operations involving the cid parameter, adding proper input validation, and conducting a broader code review to identify similar injection points in the application.

Fix this in Classified Ads Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-3672 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-3672 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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