CVE-2025-56746: n/a
Source CVE Database V5
Not known to be exploited · CVSS 2.2 Low · fixed in 5.14 : update affected systems when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.14
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
1. Immediately implement session ID regeneration upon successful user authentication within the LMS to prevent session fixation. 2. 3. Conduct a thorough review of session management configurations and enforce secure cookie attributes such as HttpOnly, Secure, and SameSite. 4. Monitor session activity logs for anomalies indicative of session hijacking attempts, such as multiple logins from different IP addresses using the same session ID. 5. Educate users and administrators about the risks of session fixation and encourage practices such as logging out after sessions and avoiding shared devices. 6. Consider implementing multi-factor authentication (MFA) to reduce the impact of session hijacking. 7. Isolate and segment LMS infrastructure to limit potential lateral movement if a session is compromised. 8. Regularly audit and test the LMS environment for session management vulnerabilities using penetration testing or automated scanning tools.
Description
Creativeitem Academy LMS up to and including 5.13 does not regenerate session IDs upon successful authentication, enabling session fixation attacks where attackers can hijack user sessions by predetermining session identifiers.