dbcve.org
Php NukeApplication · Francisco Burzi

CVE-2004-0738

HIGH · 7.5 CVSS v2.0 Published 2004-07-27
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
Multiple SQL injection vulnerabilities in the Search module in Php-Nuke allow remote attackers to execute arbitrary SQL via the (1) min or (2) categ parameters.

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

SQL injection vulnerabilities exist in Php-Nuke's Search module where the 'min' and 'categ' parameters are not properly sanitized before being used in database queries. Remote attackers can inject arbitrary SQL commands through these parameters to access, modify, or delete database contents.

MitigationImplement strict input validation and use parameterized queries (prepared statements) for all database queries involving the 'min' and 'categ' parameters in the Search module.

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 NukeApplication
Affected:= 8.0_final

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 if Php-Nuke is installed
    Look for typical Php-Nuke files and directories such as /modules/Your_Account/, /includes/, or config.php in the web root. Check for the presence of index.php with Php-Nuke content or footer branding.
    Affected if Php-Nuke software is found on the server.
  2. Determine the installed Php-Nuke version
    Check the version file or common version disclosure locations. In Php-Nuke 8.0_final, look for a version.php file, or check the main index.php or includes/config.php for version strings. The version may also appear in the admin panel footer or in meta tags.
    Affected if The installed version is 8.0_final.
  3. Verify the Search module is accessible
    Check if the Search module is enabled and accessible by attempting to access /modules.php?name=Search or /modules/Search/ on the web server. Also check the modules table in the database if database access is available.
    Affected if The Search module is installed and publicly accessible.
  4. Inspect the Search module code for vulnerable parameters
    Locate the Search module file (typically modules/Search/index.php or modules/Search/search.php). Examine the code for usage of 'min' and 'categ' GET or POST parameters that are directly inserted into SQL queries without proper sanitization or use of prepared statements.
    Affected if The code uses 'min' or 'categ' parameters directly in SQL queries without sanitization or parameterized queries.
  5. Review web server and database logs for SQL injection attempts
    Examine web server access logs (Apache access_log, Nginx access.log) and database query logs for suspicious requests containing SQL syntax in the 'min' or 'categ' parameters, such as requests to /modules.php?name=Search&min=1' or similar patterns.
    Affected if Logs contain SQL injection payloads targeting the 'min' or 'categ' parameters.

You are affected if Php-Nuke 8.0_final is installed, the Search module is enabled, and the vulnerable 'min' or 'categ' parameters are used in unsanitized SQL 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 strict input validation and use parameterized queries (prepared statements) for all database queries involving the 'min' and 'categ' parameters in the Search module.

Fix this in Php Nuke Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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