CVE-2010-1613 json
Moodle Session Fixation vulnerability
published 16y ago modified 4mo ago also GHSA-j5rc-cr5w-vfg6 , EUVD-2010-1639
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
Moodle 1.8.x and 1.9.x before 1.9.8 does not enable the "Regenerate session id during login" setting by default, which makes it easier for remote attackers to conduct session fixation attacks.
Patch / fix
- packagist moodle/moodle 1.9.8
Is CVE-2010-1613 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2010-1613 updated
Moodle: Multiple security fixes in 1.8.12 upstream release
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.81% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | moodle/moodle | >=1.8.0, <1.9.8 |
1.9.8 |
Classification
References
-
lists.opensuse.org
/opensuse-security-announce/2010-05/msg00001.html
vendor-advisory, web
-
vupen.com
/english/advisories/2010/1107
vdb-entry
- moodle.org /security/
-
nvd.nist.gov
/vuln/detail/CVE-2010-1613
advisory
-
github.com
/moodle/moodle
package
-
moodle.org
/security
web
Sources
- CVE List CVE-2010-1613
- GitHub Advisory GHSA-j5rc-cr5w-vfg6
- NVD CVE-2010-1613
Fencer Intel 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.