CVE-2011-3780
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 iCalendar 2.4 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by rss/rss_common.php and certain other files.
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 iCalendar 2.4 contains a path disclosure vulnerability where directly requesting certain PHP files (such as rss/rss_common.php) causes the application to output error messages that reveal the full server installation path. This information can aid attackers in reconnaissance for further exploits.
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.4CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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.
-
Confirm PHP iCalendar versionLocate the version file or check the main application file (e.g., index.php, about.php, or a VERSION file) for the installed version stringAffected if The installed version is exactly 2.4 (version 2.4)
-
Identify accessible PHP files in the applicationLocate PHP files in subdirectories such as rss/, functions/, or includes/ that may be directly accessible via web requestAffected if Files like rss/rss_common.php or similar include files exist and are directly web-accessible
-
Test for path disclosure via direct file accessUse a web browser or curl to directly request the vulnerable PHP file (e.g., http://[host]/[path]/rss/rss_common.php) and observe any error outputAffected if The response contains error messages that display the full server filesystem path (e.g., /var/www/html/...)
-
Check PHP error display configurationInspect php.ini or use phpinfo() to verify the display_errors settingAffected if display_errors is set to On in the PHP configuration
You are affected if PHP iCalendar version 2.4 is installed and direct web access to certain PHP files outputs error messages that reveal the server filesystem path.
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 PHP error display and warnings in production php.ini (display_errors=Off, error_reporting=E_ALL), and modify vulnerable files to use proper include/require statements with access controls instead of direct execution.
- Consultation1.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3780 — 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-2011-3780 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