LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25970: Camaleon CMS - Insufficient Session Expiration after Password Change

Camaleon CMS 0.1.7 to 2.6.0 doesn’t terminate the active session of the users, even after the admin changes the user’s password. 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

Camaleon CMS failed to end an already logged-in user's session after an administrator changed that user's password. That means password resets may not immediately remove access for a person or account whose browser session is still active.

Executive priority

Prioritize remediation where Camaleon CMS supports business-critical content, privileged users, or external administration. This weakness can weaken incident response by leaving access alive after a password reset.

Technical view

CVE-2021-25970 is a CWE-613 session-expiration flaw in Camaleon CMS, described as affecting versions 0.1.7 to 2.6.0. Existing authenticated sessions remain valid after an admin password change, undermining account recovery and access removal workflows.

Likely exposure

Exposure is limited to organizations running Camaleon CMS in the affected version range, especially admin-accessible or internet-facing deployments where password resets are used to contain suspected account compromise.

Exploitation context

The source bundle does not show KEV listing or confirmed active exploitation. The practical risk is persistence of an already active session after a password change, not a source-supported unauthenticated remote takeover claim.

Researcher notes

Evidence is concise and centered on session invalidation after admin password changes. The bundle provides CVSS 3.1 score 8.8, CWE-613, and an upstream commit reference, but no KEV status, exploit report, or explicit fixed release version.

Mitigation direction

  • Identify any Camaleon CMS deployments and their versions.
  • Review vendor guidance and the referenced upstream commit for the intended correction.
  • Upgrade or patch using vendor-supported Camaleon CMS releases where available.
  • After password changes, revoke active sessions through supported administrative or server controls.
  • Monitor affected sites for post-reset activity from previously active accounts.

Validation and detection

  • Confirm whether deployed Camaleon CMS versions fall within 0.1.7 to 2.6.0.
  • Verify whether the referenced upstream fix is present in deployed code.
  • Review account logs for activity after administrative password resets.
  • Confirm incident playbooks include session revocation after credential resets.
Prepared
Confidence
high
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-25970 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-25970Attack 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
camaleon_cmscamaleon_cms0.1.7, 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.