CVE-2009-3702
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 absolute path traversal vulnerabilities in PHP-Calendar 1.1 allow remote attackers to include and execute arbitrary local files via a full pathname in the configfile parameter to (1) update08.php or (2) update10.php. NOTE: in some environments, this can be leveraged for remote file inclusion by using a UNC share pathname or an ftp, ftps, or ssh2.sftp URL.
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-Calendar 1.1 contains absolute path traversal vulnerabilities in update08.php and update10.php where the configfile parameter accepts full file paths without validation, allowing local file inclusion and arbitrary code execution. In permissive server configurations, this can be exploited for remote file inclusion via UNC paths or FTP/SFTP URLs.
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= 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
- 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.
-
Identify PHP-Calendar installation and versionLocate the PHP-Calendar installation directory on your web server. Look for a version file, or check the source code for a version identifier. Common locations include /var/www/html/calendar, /www/calendar, or check your web root for the calendar directory.Affected if The installed version is exactly 1.1 (no patches applied)
-
Verify vulnerable update scripts existCheck whether update08.php and update10.php files exist in the PHP-Calendar installation directory. These files handle database updates and accept the configfile parameter.Affected if Both update08.php and update10.php exist and are web-accessible
-
Confirm configfile parameter is processedInspect update08.php and update10.php source code to verify they accept and process a configfile parameter without sanitizing file paths.Affected if The scripts accept a configfile parameter that is used in include/require statements without path validation
-
Check PHP allow_url_fopen settingReview your php.ini configuration or run phpinfo() to check the value of allow_url_fopen. This setting controls whether PHP can open remote files via URLs.Affected if allow_url_fopen is enabled (set to On)
-
Check PHP allow_url_include settingReview your php.ini configuration or run phpinfo() to check the value of allow_url_include. This setting controls whether include/require can use remote URLs.Affected if allow_url_include is enabled (set to On), allowing RFI via UNC paths or FTP/SFTP URLs
You are affected if PHP-Calendar 1.1 is installed with update08.php and update10.php accessible, and these scripts process the configfile parameter without validation, especially if allow_url_fopen or allow_url_include are enabled.
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 PHP-Calendar; if no update exists, implement strict input validation on the configfile parameter to only accept expected values, and disable allow_url_fopen and allow_url_include in php.ini.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-3702 — 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-3702 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