CVE-2009-0729
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 directory traversal vulnerabilities in Page Engine CMS 2.0 Basic and Pro allow remote attackers to include and execute arbitrary local files via directory traversal sequences in the fPrefix parameter to (1) modules/recent_poll_include.php, (2) modules/login_include.php, and (3) modules/statistics_include.php and (4) configuration.inc.php in includes/. 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 · moderate confidencePage Engine CMS 2.0 contains multiple local file inclusion vulnerabilities via the fPrefix parameter in four files (recent_poll_include.php, login_include.php, statistics_include.php, and configuration.inc.php). Attackers can use directory traversal sequences (../) to access and potentially execute arbitrary local files, leading to information disclosure or remote code execution.
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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Confirm Lingx Page Engine CMS installationLocate the CMS installation by searching for the file 'configuration.inc.php' or checking web server document roots for Page Engine CMS directories. Check version.php or any version file for version number 2.0.Affected if The system has Lingx Page Engine CMS version 2.0 installed.
-
Identify vulnerable include filesCheck the web root for the presence of these files in the CMS directory: recent_poll_include.php, login_include.php, statistics_include.php, and configuration.inc.php.Affected if Any of these four files exist in the CMS installation directory.
-
Verify PHP allow_url_include settingCreate a PHP info file (info.php) with content '<?php phpinfo(); ?>' and access it via browser, or check php.ini for the 'allow_url_include' directive.Affected if allow_url_include is enabled (set to On).
-
Test fPrefix parameter accessibilityAttempt to access one of the vulnerable files directly via HTTP request with a test traversal pattern, e.g., '?fPrefix=../' appended to the file URL. Check if the application processes the parameter without validation.Affected if The fPrefix parameter is accepted and processed by the vulnerable files without rejecting directory traversal sequences.
A system is affected if it runs Lingx Page Engine CMS version 2.0 with the vulnerable include files present and accessible via web, where the fPrefix parameter accepts unsanitized input.
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 dataImplement strict input validation on the fPrefix parameter to reject directory traversal sequences; use whitelist-based path filtering and ensure PHP's allow_url_include is disabled.
- 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-2009-0729 — 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-2009-0729 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