dbcve.org
Php NukeApplication · Francisco Burzi

CVE-2005-1386

MEDIUM · 5.0 CVSS v2.0 Published 2005-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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
PHP-Nuke 7.6 and earlier allows remote attackers to obtain sensitive information via a direct request to (1) ipban.php, (2) db.php, (3) lang-norwegian.php, (4) lang-indonesian.php, (5) lang-greek.php, (6) a request to Web_Links with the portuguese language (lang-portuguese.php), (7) a request to Web_Links with the indonesian language (lang-indonesian.php), (8) a request to the survey module with the indonesian language (lang-indonesian.php), (9) a request to the Reviews module with the portuguese language, or (10) a request to the Journal module with the portuguese language, which reveal 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

This is an information disclosure vulnerability in PHP-Nuke 7.6 and earlier where direct requests to multiple PHP files (ipban.php, db.php, and various lang-*.php files in Web_Links, Survey, Reviews, and Journal modules) expose full server file paths in error messages. An attacker can use this path information for reconnaissance to identify system structure and potentially craft more targeted attacks.

MitigationDisable PHP error display (set display_errors=Off in php.ini) or upgrade to a patched version of PHP-Nuke to prevent path disclosure. Additionally, ensure these include files properly handle direct access attempts.

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:= 6.0= 6.5= 6.5_beta1= 6.5_final= 6.5_rc1= 6.5_rc2= 6.5_rc3= 6.6= 6.7= 6.9= 7.0= 7.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
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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 PHP-Nuke installation
    Search web root directories for PHP-Nuke files such as mainfile.php, config.php, or the modules/ directory structure commonly found in PHP-Nuke installations.
    Affected if PHP-Nuke is present on the server
  2. Determine PHP-Nuke version
    Open the mainfile.php or version.php file in the PHP-Nuke root directory and locate the version definition string.
    Affected if Installed version matches 6.0 through 7.0_final as listed in the affected versions
  3. Identify vulnerable PHP files
    Check for the existence of ipban.php and db.php in the PHP-Nuke root directory, and look for lang-*.php files inside the modules/Web_Links, modules/Survey, modules/Reviews, and modules/Journal directories.
    Affected if Any of these files exist in the expected locations
  4. Verify PHP error display setting
    Create a PHP file with phpinfo() content or check php.ini for the display_errors directive. It should be set to On for this vulnerability to be exploitable.
    Affected if display_errors is enabled (set to On) in PHP configuration
  5. Test for path disclosure
    Send a direct HTTP request to one of the vulnerable files (ipban.php or db.php in the root, or any lang-*.php file in the affected modules) and observe if error messages reveal absolute server file paths.
    Affected if Direct access to these files produces error messages containing full server paths

You are affected if PHP-Nuke versions 6.0 through 7.0_final are installed, the vulnerable files are accessible, and PHP display_errors is enabled, allowing path disclosure in error messages.

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

Disable PHP error display (set display_errors=Off in php.ini) or upgrade to a patched version of PHP-Nuke to prevent path disclosure. Additionally, ensure these include files properly handle direct access attempts.

Fix this in Php Nuke 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 help mitigating

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-2005-1386 — 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-2005-1386 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