Noahs ClassifiedsApplication · Phpoutsourcing

CVE-2006-1332

MEDIUM · 6.4 CVSS v2.0 Published 2006-03-21
Fix available
A fix is available. Upgrade to after 1.3 or later.
See remediation →
73/100
Remediation priority · Elevated
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
Noah's Classifieds 1.3 and earlier allows remote attackers to obtain sensitive information via an invalid list parameter in the showdetails method to index.php, which reveals the path in an error message.

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 confidence

Noah's Classifieds 1.3 and earlier allows remote attackers to obtain the server's installation path by supplying an invalid list parameter to the showdetails method in index.php, which causes the application to expose the full path in an error message.

MitigationImplement input validation for the list parameter and configure the application to display generic error messages rather than detailed error traces that expose file paths.

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
Noahs ClassifiedsApplication
Affected:<= 1.3

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
None
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:N/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. Confirm Noah's Classifieds is installed
    Locate index.php file in the web root and verify it is the Phpoutsourcing Noah's Classifieds application by examining the application source code or login page for product identification
    Affected if The application is present on the server
  2. Determine the installed version
    Check the application version by reviewing source files, a version.php file, or any version information displayed in the admin interface or README file included with the installation
    Affected if The version is 1.3 or earlier
  3. Test for path disclosure vulnerability
    Send an HTTP request to index.php with an invalid list parameter value, for example: index.php?do=showdetails&list=invalidvalue or similar parameter pattern that triggers the showdetails method with a malformed input
    Affected if The response returns an error message containing the full server file system path (such as /home/user/public_html or C:\inetpub\wwwroot)
  4. Verify error display is enabled
    Check if PHP display_errors is enabled or if the application is configured to show detailed error messages rather than generic ones
    Affected if Detailed PHP error traces or full paths are visible in the response

The environment is affected if Noah's Classifieds version 1.3 or earlier is installed and accessing index.php with an invalid list parameter exposes the full server path in an error message.

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
Upgrade available Upgrade to a release after 1.3
Interim mitigation

Implement input validation for the list parameter and configure the application to display generic error messages rather than detailed error traces that expose file paths.

Fix this in Noahs Classifieds Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-1332 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-1332 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