CVE-2005-3949 json
Multiple SQL injection vulnerabilities in WebCalendar 1.0.1 allow remote attackers to execute arbitrary SQL commands via the (1) startid pa…
published 2005-12-01 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-3944
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
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.
Exploit prediction
2.11% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
References
-
debian.org
/security/2006/dsa-1002
vendor-advisory
-
secunia.com
/advisories/17784
third-party-advisory, vendor-advisory
-
ush.it
/2005/11/28/webcalendar-multiple-vulnerabilities
vendor-advisory
-
securityfocus.com
/archive/1/418286/100/0/threaded
mailing-list
-
securityfocus.com
/archive/1/417900/100/0/threaded
mailing-list
-
osvdb.org
/21219
vdb-entry
-
secunia.com
/advisories/19240
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/23369
vdb-entry
-
osvdb.org
/21218
vdb-entry
-
osvdb.org
/21217
vdb-entry
-
vupen.com
/english/advisories/2005/2643
vdb-entry
-
securityreason.com
/securityalert/215
third-party-advisory
-
osvdb.org
/21216
vdb-entry
- sourceforge.net /forum/forum.php?thread_id=1392833&forum_id=11587
-
securityfocus.com
/bid/15608
vdb-entry
-
securityfocus.com
/bid/15662
vdb-entry
-
securityfocus.com
/bid/15606
vdb-entry
Sources
- CVE List CVE-2005-3949
- NVD CVE-2005-3949
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.