CVE-2005-3961
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 · uneditedexport_handler.php in WebCalendar 1.0.1 allows remote attackers to overwrite WebCalendar data files via a modified 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 · moderate confidenceThe export_handler.php script in WebCalendar 1.0.1 fails to properly validate the id parameter, allowing remote attackers to manipulate file paths and overwrite arbitrary WebCalendar data files on the server. This file overwrite vulnerability could lead to data corruption or denial of service.
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.0.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.
-
Confirm WebCalendar installationLocate the WebCalendar application directory on the server. Common paths include /var/www/html/webcalendar, /www/webcalendar, or check your web server document root for a webcalendar directory.Affected if WebCalendar is not installed on the system.
-
Identify WebCalendar versionCheck the version file or header in the WebCalendar installation. Look for a version.php, README, or check the HTTP response headers when accessing the application. The affected version is 1.0.1.Affected if The installed version is WebCalendar 1.0.1.
-
Locate export_handler.phpSearch for the file export_handler.php within the WebCalendar installation directory. This is the vulnerable script mentioned in the CVE.Affected if export_handler.php exists in the WebCalendar installation.
-
Verify id parameter handlingExamine the export_handler.php script to see how the 'id' parameter is processed. Check if user-supplied input for 'id' is used in file operations without proper validation.Affected if The id parameter accepts user input and uses it in file path operations without strict validation.
-
Check file write permissionsReview the permissions on WebCalendar data directories and files. Determine if the web server user has write access to files that could be overwritten via the id parameter.Affected if The web server process can write to WebCalendar data files based on the vulnerable parameter input.
A user is affected if they are running WebCalendar version 1.0.1 with the export_handler.php script present and the id parameter accessible for manipulation.
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 id parameter to restrict it to expected values, apply proper file access controls to prevent writing outside intended directories, and upgrade to a patched version of WebCalendar if available.
- 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-2005-3961 — 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-2005-3961 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