CVE-2005-0793
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 · uneditedPHP remote file inclusion vulnerability in zpanel.php in ZPanel allows remote attackers to (1) execute arbitrary PHP code in ZPanel 2.0 or (2) include local files in ZPanel 2.5 beta 10 and earlier by modifying the page parameter.
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 confidencePHP remote file inclusion vulnerability in ZPanel's zpanel.php allows remote attackers to execute arbitrary PHP code or include local files by manipulating the 'page' parameter. This is a classic RFI vulnerability where user-supplied input is used in an include() or require() statement without proper validation.
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= 2.0= 2.5_beta= 2.5_beta9= 2.5_beta10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify ZPanel installation existsLocate ZPanel on the system by searching for the zpanel.php file, typically in the web root directory (e.g., /var/www/html/, /home/*/public_html/, or C:\inetpub\wwwroot\). Use: find /var/www -name 'zpanel.php' 2>/dev/null or dir /s /b C:\zpanel.phpAffected if ZPanel is installed and the zpanel.php file is found on the system
-
Identify installed ZPanel versionCheck the version of ZPanel by examining the source code comments in zpanel.php, or look for a VERSION file in the ZPanel installation directory. Open zpanel.php and search for version strings like '2.0', '2.5_beta', or version variables.Affected if The version matches 2.0, 2.5_beta, 2.5_beta9, or 2.5_beta10
-
Inspect the page parameter handling in zpanel.phpOpen zpanel.php and locate the code handling the 'page' parameter. Search for patterns like '$_GET['page']', '$_POST['page']', or '$_REQUEST['page']' used in include(), require(), include_once(), or require_once() statements without validation.Affected if The 'page' parameter is directly used in an include/require statement without sanitization or allowlist validation
-
Check if the vulnerable include pattern is presentLook for code similar to: include($_GET['page']); or require($_GET['page']); or include($page); where $page derives from user input without validation. Use grep: grep -n '\$_GET\['page'\]' zpanel.phpAffected if The code contains an include/require statement that uses the 'page' parameter without input validation or filtering
A system is affected if ZPanel version 2.0, 2.5_beta, 2.5_beta9, or 2.5_beta10 is installed and the zpanel.php file contains the 'page' parameter being used in an include/require statement without validation.
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 dataUpgrade to a patched version of ZPanel or implement strict input validation/sanitization on the page parameter to ensure only allowed files can be included. Disable allow_url_fopen in PHP configuration as an additional defense-in-depth measure.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-0793 — 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-2005-0793 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