Php FiApplication · PHP
CVE-1999-0346
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 · uneditedCGI PHP mlog script allows an attacker to read any file on the target server.
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 · moderate confidenceThe mlog CGI script contains a path traversal vulnerability that allows remote attackers to read arbitrary files on the server by manipulating file path parameters in HTTP requests.
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 FiApplication
all versionsCVSS 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.
-
Locate the mlog CGI script on the systemSearch the web server document root and CGI directories for a file named 'mlog' or 'mlog.cgi'. Common search commands: `find /var/www -name 'mlog*' 2>/dev/null` or `find /usr/lib/cgi-bin -name 'mlog*' 2>/dev/null`Affected if The mlog or mlog.cgi file exists in any web-accessible directory
-
Verify the script is executable and accessible via HTTPCheck file permissions with `ls -la <path_to_mlog>` and confirm the web server can serve it. Attempt a simple HTTP request to the script URL (e.g., `curl -I http://your-server/cgi-bin/mlog`) to confirm it respondsAffected if The script returns an HTTP 200 or similar response, indicating it is reachable
-
Test for path traversal vulnerabilitySend a crafted request with directory traversal sequences such as `curl 'http://your-server/cgi-bin/mlog?file=../../../../etc/passwd'` and observe if the response contains contents of /etc/passwd or other sensitive filesAffected if The script returns file contents from outside its intended directory, confirming the path traversal is exploitable
-
Check if PHP Php Fi is installedSearch for PHP Php Fi installation directories: `find / -type d -name '*phpfi*' -o -name '*php-fi*' 2>/dev/null`. Also check for configuration files like config.php in web directoriesAffected if PHP Php Fi is installed and the mlog script is present within its directory structure
You are affected if the mlog CGI script exists on your server, is accessible via HTTP, and responds to traversal sequences by returning arbitrary file contents.
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 dataRemove or disable the vulnerable mlog CGI script. If the script is required, implement strict input validation to prevent directory traversal attacks.
Fix this in Php Fi
Scoped from the published advisory
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0346 — 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-1999-0346 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