WebcalendarApplication

CVE-2005-3949

HIGH · 7.5 CVSS v2.0 Published 2005-12-01

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Multiple SQL injection vulnerabilities in WebCalendar 1.0.1 allow remote attackers to execute arbitrary SQL commands via the (1) startid parameter to activity_log.php, (2) startid parameter to admin_handler.php, (3) template parameter to edit_template.php, and (4) multiple parameters to export_handler.php.

Technical summary

dbcve analysis · high confidence

Multiple SQL injection vulnerabilities in WebCalendar 1.0.1 allow remote attackers to execute arbitrary SQL commands via unsanitized user input in the startid parameter (activity_log.php, admin_handler.php), template parameter (edit_template.php), and multiple parameters (export_handler.php).

MitigationImplement proper input validation and use parameterized queries/prepared statements in the affected PHP files to prevent SQL injection attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

WebcalendarApplication

Affected:= 1.0.1

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm WebCalendar installation

Locate WebCalendar on the system by searching for the webcalendar directory or common installation paths (e.g., /var/www/html/webcalendar, /www/webcalendar, C:\inetpub\wwwroot\webcalendar). Identify the installation directory where the PHP files are hosted.

Affected if WebCalendar is not installed on the system.
Identify WebCalendar version

Check the version of WebCalendar by looking for a version file, checking the main index.php or includes file for a version constant, or examining the admin interface for version information. Common locations include version.php, about.php, or the HTML source of the main page.

Affected if The installed version is 1.0.1.
Locate vulnerable PHP files

Search for the following PHP files within the WebCalendar installation directory: activity_log.php, admin_handler.php, edit_template.php, and export_handler.php. These files handle the vulnerable parameters.

Affected if Any of these four PHP files exist in the WebCalendar installation.
Verify web accessibility of vulnerable files

Check if the identified PHP files are accessible via the web server by attempting to access them through a browser (e.g., http://[host]/webcalendar/activity_log.php). Confirm the web server serves these files.

Affected if The vulnerable PHP files are accessible over HTTP/HTTPS.
Inspect parameter handling in vulnerable files

Examine the source code of activity_log.php for the startid parameter, edit_template.php for the template parameter, and export_handler.php for multiple parameters. Check if user input is directly used in SQL queries without sanitization or parameterization.

Affected if The code uses unsanitized user input (startid, template, or export parameters) directly in SQL queries.

A system is affected if WebCalendar version 1.0.1 is installed and the vulnerable PHP files (activity_log.php, admin_handler.php, edit_template.php, export_handler.php) are accessible via the web with unsanitized user input being used in SQL queries.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Implement proper input validation and use parameterized queries/prepared statements in the affected PHP files to prevent SQL injection attacks.

Fix this in Webcalendar Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing3.0 h
Review / QA2.0 h

14.0 hours of engineering $2,490

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2005-3949 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2005-3949 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2005-3949?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 2.1%

Affects: Webcalendar

Remediation

A high-priority fix

Fix this in Webcalendar 14 hrs · Moderate

Typical engagement from $2,490

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2005-3949 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References