Skip to main content
CVE-2026-116894VulnerabilityPublished

REDAXO before 5.21.5 contains an insufficient session expiration vulnerability that allows attackers to retain account

Source GCVE Database

0
Authoritative record:CVE-2026-116894· Low 2.3

Not known to be exploited · CVSS 2.3 Low : upgrade to 5.21.5 when convenient.

Data as of 27 Oct 2026, 13:28 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 5.21.5
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade core and redaxo/core to 5.21.5.

Affected software

ProductAffectedFixed in
redaxocoreAffected
  • <5.21.5
Fixed in
  • 5.21.5
GitHubredaxo/corepkg:github/redaxo/coreOther threatsAffected
  • <5.21.5
Fixed in
  • 5.21.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in REDAXO version 5.21.5. Users should upgrade to version 5.21.5 or later to ensure that sessions and stay-logged-in keys are properly invalidated upon password changes, preventing attackers from retaining access.

Description

REDAXO versions prior to 5.21.5 have a vulnerability related to insufficient session expiration. This flaw allows attackers who have obtained a user's session ID or stay-logged-in cookie to maintain backend access even after the user changes their password. The stay-logged-in cookie remains valid for up to three months, enabling prolonged unauthorized access.

References

Community reviews

Loading reviews…