# CVE-2026-46657: Bludit insufficient session expiration for disabled accounts

Source: https://junglewise.ai/threats/cve-2026-46657-bludit-insufficient-session-expiration-for-disabled-accounts  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-08. Updated: 2026-06-08  
License: CC BY 4.0 with a link back

CVE-2026-46657 · Severity: high · CVSS 7.1 · Published 2026-06-08

Bludit is a content management system used to build and manage websites. A security flaw allows users whose accounts have been disabled by an administrator to continue accessing the system if they have a 'Remember Me' cookie active. This means a terminated employee or revoked user could still modify site content or access private data despite their account being officially deactivated.

Technologies: [Bludit](https://junglewise.ai/threats/technologies/bludit). Vendors: [Bludit](https://junglewise.ai/threats/vendors/bludit).

## Quick answers

**Is CVE-2026-46657 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-46657 being exploited in the wild.

**How severe is CVE-2026-46657?** High severity, with a CVSS score of 7.1, published 8 June 2026.

**Which products and versions are affected?** Bludit < 3.22.0.

**Is there a fix for CVE-2026-46657?** A patch was published on 2026-05-11: Version 3.22.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-46657 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-46657?** Check whether you run Bludit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A vulnerability exists in the user management logic of Bludit CMS within the disableUser() function in bl-kernel/users.class.php. While the application invalidates the password field by prefixing it with a '!' character, it fails to clear the tokenAuth and tokenRemember fields in the JSON database (bl-content/databases/users.php). An attacker with a pre-existing, valid 'Remember Me' cookie can bypass the account disablement because the authentication subsystem validates the cookie against the uncleared database tokens. This allows a deactivated user to maintain a valid session with their original privileges. The issue is resolved in version 3.22.0 by ensuring these tokens are cleared upon account deactivation.

## Affected products

- Bludit Bludit < 3.22.0

## Timeline

- 2026-05-11: patched: Version 3.22.0 released
- 2026-05-19: advisory: GitHub Security Advisory published
- 2026-06-08: disclosed: CVE published to NVD

## References

- [https://github.com/bludit/bludit/releases/tag/3.22.0](https://github.com/bludit/bludit/releases/tag/3.22.0)
- [https://github.com/bludit/bludit/security/advisories/GHSA-ggqg-xvx6-hgwh](https://github.com/bludit/bludit/security/advisories/GHSA-ggqg-xvx6-hgwh)

## Related threats

- [Bludit stored cross-site scripting in logo upload](https://junglewise.ai/threats/cve-2026-72576-bludit-stored-cross-site-scripting-in-logo-upload)
- [Bludit directory traversal in api/plugin.php](https://junglewise.ai/threats/cve-2026-50869-bludit-directory-traversal-in-api-plugin-php)
- [Bludit CMS remote code execution in API Plugin](https://junglewise.ai/threats/cve-2026-38329-bludit-cms-remote-code-execution-in-api-plugin)
- [Bludit CMS broken access control via ghost sessions](https://junglewise.ai/threats/cve-2026-46656-bludit-cms-broken-access-control-via-ghost-sessions)
- [Bludit CMS reflected XSS in search plugin](https://junglewise.ai/threats/cve-2026-41456-bludit-cms-reflected-xss-in-search-plugin)