CVE-2021-25966: CWE-613 Insufficient Session Expiration in OrchardCore Users
In “Orchard core CMS” application, versions 1.0.0-beta1-3383 to 1.0.0 are vulnerable to an improper session termination after password change. When a password has been changed by the user or by an administrator, a user that was already logged in, will still have access to the application even after the password was changed.
AI Analysis
Technical Summary
CVE-2021-25966 is a high-severity vulnerability affecting OrchardCore CMS versions from 1.0.0-beta1-3383 up to 1.0.0. The issue stems from insufficient session expiration controls (CWE-613) within the OrchardCore Users module. Specifically, when a user or administrator changes a password, existing authenticated sessions for that user are not invalidated or terminated. This means that any session active prior to the password change remains valid, allowing continued access to the application despite the password update. The vulnerability arises due to improper session management logic that fails to enforce session revocation upon credential changes. Exploitation requires no privileges beyond user-level access and only user interaction to trigger the password change. The CVSS 3.1 base score is 8.8 (high), reflecting the network attack vector, low attack complexity, no privileges required, user interaction required, and high impact on confidentiality, integrity, and availability. The vulnerability can lead to unauthorized persistent access by an attacker or malicious insider who has gained access to a session token before a password reset, effectively bypassing the intended security control of password changes to terminate sessions. Although no known exploits are currently reported in the wild, the vulnerability presents a significant risk to organizations using affected OrchardCore versions, especially where sensitive data or critical services are managed through the CMS. The lack of session invalidation undermines the security benefits of password changes and can facilitate lateral movement or prolonged unauthorized access within the system.
Potential Impact
For European organizations deploying OrchardCore CMS in the affected versions, this vulnerability poses a critical risk to user account security and overall system integrity. Attackers or insiders who have compromised session tokens can maintain access even after password resets, potentially leading to data breaches, unauthorized content manipulation, or disruption of services. This is particularly concerning for organizations handling sensitive personal data under GDPR, as unauthorized access could result in data exposure and regulatory penalties. The vulnerability also undermines incident response processes, as password changes are a common remediation step to revoke access. The persistence of sessions post-password change can delay detection and containment of breaches. Additionally, the integrity of website content and availability of services managed by OrchardCore could be compromised, impacting business continuity and reputation. Given the high CVSS score and the critical nature of session management in access control, European enterprises using OrchardCore CMS should prioritize addressing this vulnerability to maintain compliance and security posture.
Mitigation Recommendations
1. Upgrade OrchardCore CMS to a version beyond 1.0.0 where this vulnerability is fixed, or apply vendor-provided patches if available. 2. Implement custom session management logic to forcibly invalidate all active sessions upon password changes if upgrading is not immediately feasible. This can be done by tracking session tokens with timestamps and comparing them against the last password change time. 3. Enforce multi-factor authentication (MFA) to reduce the risk of session token misuse. 4. Monitor active sessions and implement session timeout policies to limit session lifetime. 5. Conduct regular audits of user sessions and access logs to detect anomalous persistent sessions. 6. Educate users and administrators on the importance of logging out and session hygiene, especially after password changes. 7. If possible, integrate additional security controls such as Web Application Firewalls (WAF) to detect suspicious session activities. 8. Review and enhance incident response plans to include checks for session persistence after credential changes.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Belgium, Italy, Spain
CVE-2021-25966: CWE-613 Insufficient Session Expiration in OrchardCore Users
Description
In “Orchard core CMS” application, versions 1.0.0-beta1-3383 to 1.0.0 are vulnerable to an improper session termination after password change. When a password has been changed by the user or by an administrator, a user that was already logged in, will still have access to the application even after the password was changed.
AI-Powered Analysis
Technical Analysis
CVE-2021-25966 is a high-severity vulnerability affecting OrchardCore CMS versions from 1.0.0-beta1-3383 up to 1.0.0. The issue stems from insufficient session expiration controls (CWE-613) within the OrchardCore Users module. Specifically, when a user or administrator changes a password, existing authenticated sessions for that user are not invalidated or terminated. This means that any session active prior to the password change remains valid, allowing continued access to the application despite the password update. The vulnerability arises due to improper session management logic that fails to enforce session revocation upon credential changes. Exploitation requires no privileges beyond user-level access and only user interaction to trigger the password change. The CVSS 3.1 base score is 8.8 (high), reflecting the network attack vector, low attack complexity, no privileges required, user interaction required, and high impact on confidentiality, integrity, and availability. The vulnerability can lead to unauthorized persistent access by an attacker or malicious insider who has gained access to a session token before a password reset, effectively bypassing the intended security control of password changes to terminate sessions. Although no known exploits are currently reported in the wild, the vulnerability presents a significant risk to organizations using affected OrchardCore versions, especially where sensitive data or critical services are managed through the CMS. The lack of session invalidation undermines the security benefits of password changes and can facilitate lateral movement or prolonged unauthorized access within the system.
Potential Impact
For European organizations deploying OrchardCore CMS in the affected versions, this vulnerability poses a critical risk to user account security and overall system integrity. Attackers or insiders who have compromised session tokens can maintain access even after password resets, potentially leading to data breaches, unauthorized content manipulation, or disruption of services. This is particularly concerning for organizations handling sensitive personal data under GDPR, as unauthorized access could result in data exposure and regulatory penalties. The vulnerability also undermines incident response processes, as password changes are a common remediation step to revoke access. The persistence of sessions post-password change can delay detection and containment of breaches. Additionally, the integrity of website content and availability of services managed by OrchardCore could be compromised, impacting business continuity and reputation. Given the high CVSS score and the critical nature of session management in access control, European enterprises using OrchardCore CMS should prioritize addressing this vulnerability to maintain compliance and security posture.
Mitigation Recommendations
1. Upgrade OrchardCore CMS to a version beyond 1.0.0 where this vulnerability is fixed, or apply vendor-provided patches if available. 2. Implement custom session management logic to forcibly invalidate all active sessions upon password changes if upgrading is not immediately feasible. This can be done by tracking session tokens with timestamps and comparing them against the last password change time. 3. Enforce multi-factor authentication (MFA) to reduce the risk of session token misuse. 4. Monitor active sessions and implement session timeout policies to limit session lifetime. 5. Conduct regular audits of user sessions and access logs to detect anomalous persistent sessions. 6. Educate users and administrators on the importance of logging out and session hygiene, especially after password changes. 7. If possible, integrate additional security controls such as Web Application Firewalls (WAF) to detect suspicious session activities. 8. Review and enhance incident response plans to include checks for session persistence after credential changes.
Affected Countries
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Mend
- Date Reserved
- 2021-01-22T00:00:00.000Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d983bc4522896dcbedb25
Added to database: 5/21/2025, 9:09:15 AM
Last enriched: 6/25/2025, 10:32:35 AM
Last updated: 2/7/2026, 4:07:27 PM
Views: 53
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2090: SQL Injection in SourceCodester Online Class Record System
MediumCVE-2026-2089: SQL Injection in SourceCodester Online Class Record System
MediumCVE-2026-2088: SQL Injection in PHPGurukul Beauty Parlour Management System
MediumCVE-2026-2087: SQL Injection in SourceCodester Online Class Record System
MediumCVE-2026-2086: Buffer Overflow in UTT HiPER 810G
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.