CVE-2025-53642
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedhaxcms-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe logout function in HAXcms (both Node.js and PHP backends) fails to terminate the user's server-side session and does not clear authentication cookies. Critically, the application incorrectly issues a refresh token upon logout, allowing continued authenticated access despite the user attempting to log out. This enables session hijacking where an attacker with access to the same browser or cached credentials can maintain access after logout.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 11.0.6< 11.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify HAXcms backend typeDetermine if your HAXcms installation uses the Node.js or PHP backend. Check your server configuration, hosting environment, or application entry point to identify which backend is in use.Affected if The backend is HAXcms Node.js or PHP without a specific version indicator matching >= 11.0.6
-
Check installed HAXcms versionFor Node.js: inspect package.json or run 'npm list haxcms' in the project directory. For PHP: check for a version file, composer.json, or the version displayed in the admin panel footer.Affected if The version number returned is less than 11.0.6 (e.g., 11.0.5, 11.0.0, 10.x, etc.)
-
Verify session termination on logoutLog into HAXcms, then call the logout endpoint (typically /api/user/logout or similar), then attempt to use the previous session token or refresh token to access protected endpoints. Check if the previously authenticated request still succeeds.Affected if After calling logout, API requests with the prior session or refresh token still return successful authenticated responses instead of 401 unauthorized errors.
-
Inspect logout response for refresh tokenCapture the HTTP response from the logout endpoint. Examine the response body or cookies for the presence of a refresh token being issued or returned upon logout.Affected if The logout response contains a refresh token, new authentication token, or session cookie when it should only return a success status with no credentials.
You are affected if your installed HAXcms version is below 11.0.6 and your logout endpoint either fails to invalidate the session or issues new authentication tokens upon logout.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped11.0.6
Upgrade to HAXcms version 11.0.6 which properly invalidates sessions, clears cookies, and removes the erroneous refresh token issuance on logout.
Upgrade to haxcms version 11.0.6 (both Node.js and PHP variants)
- 1. Back up your current haxcms installation (database and files)
- 2. Upgrade haxcms-nodejs to version 11.0.6 or later, or upgrade haxcms-php to version 11.0.6 or later depending on your deployment
- 3. Clear any existing user sessions or cookies that may have been issued prior to the upgrade
- 4. Verify the logout function now properly terminates the session and clears cookies without issuing a refresh token
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53642 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-53642 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data