Skip to content
Fencer Vulns
medium 6.8

CVE-2005-1374 json

Multiple cross-site scripting (XSS) vulnerabilities in Claroline 1.5.3 through 1.6 Release Candidate 1, and possibly Dokeos, allow remote a…

published 2005-05-02 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-1377

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.9%
EPSS 4.9% chance of exploitation in 30 days, percentile 92%
public exploits
3
Exploit-DB

Summary

Multiple cross-site scripting (XSS) vulnerabilities in Claroline 1.5.3 through 1.6 Release Candidate 1, and possibly Dokeos, allow remote attackers to inject arbitrary web script or HTML via (1) exercise_result.php, (2) exercice_submit.php, (3) agenda.php, (4) learningPathList.php, (5) learningPathAdmin.php, (6) learningPath.php, (7) userLog.php, (8) tool parameter to toolaccess_details.php, (9) data parameter to user_access_details.php, or (10) coursePath parameter to myagenda.php.

Patch / fix

Timeline

  1. First public exploit (EDB-25551)
  2. Published

Exploit prediction

4.86% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-25551 Claroline 1.5/1.6 - 'myagenda.php?coursePath' Cross-Site Scripting webapps, 2005-04-27
  • EDB-25550 Claroline 1.5/1.6 - 'user_access_details.php?data' Cross-Site Scripting webapps, 2005-04-27
  • EDB-25549 Claroline 1.5/1.6 - 'toolaccess_details.php?tool' Cross-Site Scripting webapps, 2005-04-27
  • securityfocus.com http://www.securityfocus.com/bid/13407 referenced PoC, tagged "exploit" by a source, unverified
  • secunia.com http://secunia.com/advisories/15161 referenced PoC, tagged "exploit" by a source, unverified
  • claroline.net http://www.claroline.net/news.php#85 referenced PoC, tagged "exploit" by a source, unverified
  • securitytracker.com http://securitytracker.com/id?1013822 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

References

Sources

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.