CVE-2025-26844
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 · uneditedAn issue was discovered in Znuny through 7.1.3. A cookie is set without the HttpOnly flag.
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 · moderate confidenceZnuny through version 7.1.3 sets one or more cookies without the HttpOnly flag, allowing client-side scripts to access these cookies via XSS vulnerabilities. This enables attackers to steal session identifiers and impersonate users, which explains the critical CVSS score.
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<= 7.1.3CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Determine installed Znuny versionLocate and inspect the Znuny version file or use the system's package manager to query the installed Znuny version (e.g., rpm -q, dpkg -l, or check a version file in the Znuny installation directory). Compare the version number to the affected range: any version 7.1.3 or lower is within the affected range.Affected if Installed Znuny version is 7.1.3 or lower
-
Identify cookie configuration locationLocate the Znuny configuration files that govern cookie behavior, typically found in the application configuration or kernel settings. Look for session or cookie-related configuration parameters.Affected if Cookie configuration exists and can be inspected
-
Inspect session cookies for HttpOnly flagAccess Znuny's web interface and use browser developer tools (Application tab > Cookies) or capture an HTTP response from the server to examine the Set-Cookie headers. Check each cookie for the presence or absence of the HttpOnly attribute in the Set-Cookie header.Affected if Any session-related cookie (such as session ID, authentication, or user tokens) is present without the HttpOnly attribute in the Set-Cookie header
-
Verify XSS exposure contextAssess whether user-generated content or third-party integrations exist in the Znuny environment that could execute JavaScript in a user's browser, as this would enable cookie theft via XSS if HttpOnly is missing.Affected if The application accepts and renders user input in a way that could permit XSS attacks, and session cookies lack HttpOnly protection
The environment is affected if Znuny version is 7.1.3 or lower AND at least one session-related cookie is set without the HttpOnly flag, especially when XSS vectors exist in the application.
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 · scopedAdd the HttpOnly flag to all session-related cookies in Znuny's cookie configuration or application code to prevent JavaScript access.
Znuny 7.1.4 or later (latest stable release)
- 1. Visit www.znuny.com or www.znuny.org to check for the latest Znuny release
- 2. Download and install the most recent stable version available (version 7.1.4 or later)
- 3. After upgrading, verify that the HttpOnly flag is now set on cookies by inspecting HTTP response headers in browser developer tools or using a web vulnerability scanner
- 4. Test application functionality to ensure the upgrade does not break existing features
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26844 — 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-26844 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