LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25966: Orchard Core CMS - Improper Session Termination after Password Change

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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Orchard Core CMS did not reliably end existing login sessions after a password was changed. If a session was already active, changing the password would not necessarily remove access, weakening account recovery and incident containment.

Executive priority

Treat as high priority for affected CMS deployments because password resets may not remove access. Prioritize confirmation of version exposure and vendor-directed remediation, especially on public sites or systems with privileged CMS users.

Technical view

CVE-2021-25966 is CWE-613 improper session termination in OrchardCore Users versions 1.0.0-beta1-3383 through 1.0.0. Existing authenticated sessions can remain valid after user or administrator password changes. CVSS 3.1 is 8.8 high.

Likely exposure

Exposure is likely limited to Orchard Core CMS deployments using the affected OrchardCore Users versions. Internet-facing CMS instances and sites relying on password resets to contain suspected account compromise have the highest practical risk.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The main abuse scenario is continued access from an already valid session after a password change, not unauthenticated remote takeover by itself.

Researcher notes

Evidence identifies the affected component and behavior, but the bundle does not provide a fixed version or exploitation reports. Keep analysis scoped to OrchardCore Users and validate behavior without publishing offensive reproduction details.

Mitigation direction

  • Identify Orchard Core CMS deployments and installed OrchardCore Users versions.
  • Check Orchard Core vendor guidance for the fixed release or recommended remediation.
  • Upgrade affected deployments when vendor guidance identifies a fixed version.
  • Force logout or revoke active sessions after password changes where supported.
  • Review incident playbooks so password resets include session invalidation checks.

Validation and detection

  • Confirm whether any deployment runs versions 1.0.0-beta1-3383 through 1.0.0.
  • Test in a controlled environment that password changes invalidate existing sessions.
  • Review authentication logs for sessions continuing after password reset events.
  • Verify operational procedures revoke sessions during account compromise response.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-613: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-25966 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2021-25966Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OrchardCoreUsers1.0.0-beta1-3383, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-613 · source CWE mapping

Insufficient Session Expiration

Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.