dbcve.org
Php NukeApplication · Phpnuke

CVE-2011-3784

MEDIUM · 5.0 CVSS v2.0 Published 2011-09-24
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
Francisco Burzi PHP-Nuke 8.0 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by themes/Odyssey/theme.php and certain other files.

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

PHP-Nuke 8.0 contains multiple PHP files that, when directly requested, expose the full server installation path in error messages. Attackers can enumerate files like themes/Odyssey/theme.php to discover sensitive path information that aids in reconnaissance and targeting subsequent attacks.

MitigationDisable PHP error display (display_errors=Off) and configure proper error handling in php.ini or application-level error handlers to prevent path disclosure.

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

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. Verify PHP-Nuke version is 8.0
    Check your installed PHP-Nuke version by accessing the admin panel or inspecting version.php in the includes directory
    Affected if The installed version is exactly 8.0 (the only affected version per this CVE)
  2. Confirm themes/Odyssey/theme.php exists
    Locate and verify the presence of the file themes/Odyssey/theme.php in your web root installation directory
    Affected if The file exists in the expected path within your PHP-Nuke installation
  3. Check PHP display_errors setting
    Create a PHPinfo page or check your php.ini file for display_errors=On
    Affected if display_errors is set to On in PHP configuration
  4. Test path disclosure via direct request
    Send an HTTP request directly to themes/Odyssey/theme.php (or other PHP files in the themes/Odyssey/ directory) and examine any error messages returned
    Affected if The error response contains the full server file system path (such as /home/user/public_html/)

You are affected if you are running PHP-Nuke 8.0, the vulnerable theme file exists, display_errors is enabled, and direct requests reveal full server paths 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 (display_errors=Off) and configure proper error handling in php.ini or application-level error handlers to prevent path disclosure.

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-2011-3784 — 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-2011-3784 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