Skip to main content
VulnerabilityPublished Updated

CVE-2025-53642: haxtheweb issues · Insufficient Session Expiration

Affects haxtheweb issuesSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium : upgrade to 11.0.6 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.0.6
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jul 2025

  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 haxtheweb/issues to 11.0.6.

Affected software

ProductAffectedFixed in
GitHubhaxtheweb/issuespkg:github/haxtheweb/issuesOther threatsAffected
  • <11.0.6
Fixed in
  • 11.0.6

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

AI-suggested

European organizations should promptly upgrade all instances of haxcms-nodejs and haxcms-php to version 11.0.6 or later, where the vulnerability is fixed. Until upgrading, organizations should implement compensating controls such as enforcing short session lifetimes and server-side session invalidation mechanisms independent of the application logout function. Monitoring and logging of session token usage can help detect anomalous reuse of tokens after logout. Employing secure cookie attributes (HttpOnly, Secure, SameSite) and ensuring all communications occur over TLS will reduce the risk of token interception. Additionally, organizations should review their token issuance policies to prevent refresh tokens from being issued on logout events. Conducting security audits of session management logic and educating developers on secure logout implementations can prevent similar issues. Finally, organizations should consider implementing multi-factor authentication to reduce the impact of compromised sessions.

Description

haxcms-nodejs and haxcms-php are backends for HAXcms. The logout function within the application does not terminate a user's session or clear their cookies. Additionally, the application issues a refresh token when logging out. This vulnerability is fixed in 11.0.6.

References

Community reviews

Loading reviews…