CVE-2004-1839
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 · uneditedMS Analysis module 2.0 for PHP-Nuke allows remote attackers to obtain sensitive information via a direct request to (1) browsers.php, (2) mstrack.php, or (3) title.php, which reveal the full path in a PHP 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 confidenceThe MS Analysis module 2.0 for PHP-Nuke contains multiple PHP files (browsers.php, mstrack.php, title.php) that expose the server's full file system path in PHP error messages when accessed directly. This information disclosure vulnerability results from improper error handling that leaves debug/error output enabled.
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= 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_finalCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check PHP-Nuke versionLocate the PHP-Nuke installation and identify its version number from configuration files or version-defining files in the web root.Affected if The installed version matches any of the following: 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, or 7.0_final.
-
Locate MS Analysis module installationSearch the web server's file system for the 'MS_Analysis' module directory, which is typically found within the PHP-Nuke modules folder.Affected if The MS Analysis module version 2.0 is installed on the PHP-Nuke system.
-
Identify vulnerable PHP filesCheck for the presence of browsers.php, mstrack.php, and title.php files within the MS_Analysis module directory.Affected if Any of these three files (browsers.php, mstrack.php, title.php) exist in the module folder.
-
Test for path disclosure via direct accessUse a web browser or curl to directly request one of the vulnerable PHP files (for example: http://your-site.com/modules/MS_Analysis/browsers.php). Observe any error messages that reveal the server's full file system path.Affected if Direct access to any of the files produces PHP error messages that expose the absolute path on the server (for example, '/var/www/html/...' or 'C:\inetpub\...').
A user is affected if they run a matching PHP-Nuke version with the MS Analysis 2.0 module installed and direct access to browsers.php, mstrack.php, or title.php reveals the server's filesystem path in error output.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable PHP error display or add proper error handling to suppress detailed error messages in the affected module files. Alternatively, remove or rename the vulnerable PHP files if they are not required for normal module operation.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-1839 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2004-1839 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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