CVE-2007-2269
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 · uneditedDirectory traversal vulnerability in top.php3 in SWsoft Plesk for Windows 8.1 and 8.1.1 allows remote attackers to read arbitrary files via a .. (dot dot) in the locale_id 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 confidenceA directory traversal vulnerability in top.php3 in SWsoft Plesk for Windows 8.1 and 8.1.1 allows remote attackers to read arbitrary files on the server by using '../' sequences in the locale_id parameter.
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= 8.1.0= 8.1.1CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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.
-
Verify Plesk for Windows installation and versionLocate the Plesk installation directory. Check the version by examining Plesk control panel files, registry keys, or theplesk version command output if available. Common installation paths include C:\Program Files\SWsoft\Plesk or similar.Affected if The installed Plesk version is exactly 8.1.0 or exactly 8.1.1
-
Confirm top.php3 file existsSearch for the file top.php3 within the Plesk web directory structure. This file is typically located in the admin or client-facing web interface directories under the Plesk installation path.Affected if The file top.php3 exists in the Plesk web directories
-
Check web interface accessibilityDetermine if the Plesk web interface (port 8443 or 80/443) is accessible from network locations. Verify that the top.php3 script is reachable via HTTP/HTTPS requests.Affected if The Plesk web interface is exposed and top.php3 is accessible via the locale_id parameter over the network
-
Inspect locale_id parameter handlingReview the top.php3 script source code to confirm it processes the locale_id parameter without proper sanitization of directory traversal sequences.Affected if The locale_id parameter accepts and acts on '../' sequences without validation
-
Verify web server configurationExamine the web server (IIS or other) configuration serving the Plesk web interface to determine if the vulnerable top.php3 endpoint is enabled and accessible.Affected if The web server configuration allows unrestricted access to the top.php3 script with the vulnerable parameter
You are affected if Plesk for Windows version 8.1.0 or 8.1.1 is installed, the top.php3 file exists, and the web interface exposing this script is accessible.
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 Plesk to a patched version beyond 8.1.1, or temporarily restrict access to top.php3 via web server configuration or network-level access controls until the upgrade can be performed.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2269 — 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-2269 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