CVE-2012-1496
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 · uneditedLocal file inclusion in WebCalendar before 1.2.5.
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 confidenceWebCalendar before version 1.2.5 contains a local file inclusion (LFI) vulnerability that allows remote attackers to read arbitrary files from the server filesystem by manipulating input parameters used in file inclusion operations.
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.2.5CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate WebCalendar installationSearch for WebCalendar files in the web server document root (commonly under /var/www/, /htdocs/, or C:\inetpub\wwwroot\). Look for directories named 'webcalendar' or 'calendar' containing PHP files.Affected if WebCalendar is found on the server
-
Determine installed WebCalendar versionOpen the file includes/settings.php or the main index.php in a text editor and search for a variable containing the version number (often labeled as '$webcalendar_version', 'VERSION', or similar). Alternatively, check the login page source for a version string.Affected if The version number found is less than 1.2.5
-
Verify PHP is being usedConfirm the WebCalendar installation contains .php file extensions and the web server is configured to process PHP scripts.Affected if PHP is enabled and processing .php files in the WebCalendar directory
-
Check if application is network-accessibleAttempt to access the WebCalendar login or main page over HTTP/HTTPS from a remote system or browser to confirm the application is exposed on the network.Affected if The WebCalendar interface is reachable via network requests
The environment is affected if WebCalendar is installed and accessible with a version lower than 1.2.5, as this version range contains the LFI vulnerability allowing arbitrary file reads.
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 data1.2.5
Upgrade WebCalendar to version 1.2.5 or later. If immediate upgrading is not feasible, implement strict input validation on all user-supplied parameters and disable PHP file inclusion functions where not required.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1496 — 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-2012-1496 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