dbcve.org
Php Script IndexApplication · PHP

CVE-2006-1559

HIGH · 7.5 CVSS v2.0 Published 2006-03-31
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 PHP Script Index allows remote attackers to execute arbitrary SQL commands via the search parameter. 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 · low confidence

SQL injection vulnerability in PHP Script Index allows remote attackers to execute arbitrary SQL commands via the search parameter.

MitigationImplement parameterized queries (prepared statements) for all database queries, especially the search parameter, and apply proper input validation and output encoding.

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
Php Script IndexApplication
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. Identify PHP Script Index installation
    Search for files matching 'script', 'index', or 'php' naming conventions in web document roots. Common paths include /var/www/, /htdocs/, or C:\inetpub\wwwroot\. Look for directories containing PHP files with 'search' functionality.
    Affected if PHP Script Index application files are present on the server
  2. Locate the search handler file
    Find PHP files that process search requests. Look for files containing 'search' in the filename or files that handle the search parameter from GET/POST requests. Search source code for '$_GET[\'search\']' or '$_POST[\'search\']' patterns.
    Affected if A search handler PHP file exists that processes the search parameter
  3. Inspect search parameter SQL handling
    Open the identified search handler file and examine how the search parameter is used in database queries. Look for patterns like 'SELECT ... WHERE ... = \'" . $_REQUEST[\'search\'] . "\'' or similar string concatenation in SQL queries.
    Affected if The search parameter is directly concatenated into SQL queries without using parameterized queries or input sanitization
  4. Verify database user privileges
    Check the database configuration file (often config.php, db.php, or similar) to identify the database credentials and user privileges configured for the application.
    Affected if The application connects to the database with a user that has broad privileges (like SELECT, INSERT, UPDATE, DELETE on multiple tables)
  5. Confirm search feature is accessible
    Access the application's search functionality through a web browser or curl request. Try to access the search page directly by navigating to the application's URL with a search parameter, such as index.php?action=search or similar.
    Affected if The search page loads and accepts user input without requiring authentication

A user is affected if PHP Script Index is installed and the search parameter is handled through direct SQL string concatenation rather than parameterized queries.

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

Implement parameterized queries (prepared statements) for all database queries, especially the search parameter, and apply proper input validation and output encoding.

Fix this in Php Script Index Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

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