dbcve.org
ZnunyApplication

CVE-2025-26847

HIGH · 7.5 CVSS v3.1 Published 2025-05-08
Fix available
A fix is available. Upgrade to after 7.1.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in Znuny before 7.1.5. When generating a support bundle, not all passwords are masked.

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 confidence

Znuny before version 7.1.5 has an information disclosure vulnerability in its support bundle generation feature. When generating a support bundle for troubleshooting or support purposes, the system fails to properly mask all passwords, potentially exposing sensitive credential data in plain text within the exported bundle.

MitigationUpgrade to Znuny version 7.1.5 or later. Until patched, avoid generating or sharing support bundles with untrusted parties, as they may contain unmasked passwords.

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
ZnunyApplication
Affected:>= 6.0.31, <= 6.0.48>= 6.5.1, <= 6.5.14>= 7.0.1, <= 7.1.6

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Znuny version
    Check the Znuny version file or admin interface. Typically found in /opt/znuny/RELEASE or via admin dashboard under 'System Administration' > 'System Information'.
    Affected if Version is >= 6.0.31 and <= 6.0.48, OR >= 6.5.1 and <= 6.5.14, OR >= 7.0.1 and <= 7.1.6
  2. Locate support bundle generation feature
    In the Znuny admin interface, navigate to the support bundle or diagnostic export feature, typically under 'Admin' > 'Support Bundle' or 'System Diagnostics' > 'Generate Support Bundle'.
    Affected if The support bundle feature exists and is accessible in the interface
  3. Verify if support bundles have been generated
    Check the var/log directory or admin interface for recent support bundle generation events. Look for .tar.gz or .zip files with timestamps indicating recent export activity.
    Affected if Any support bundles have been generated on the system
  4. Inspect a generated support bundle for unmasked passwords
    Extract any existing support bundle and search within the contained files (particularly configuration or log files) for plain-text password strings. Look for patterns like 'Password: *****' (masked) versus 'Password: mysecretpass' (unmasked).
    Affected if Any file within the bundle contains passwords in plain text rather than masked format

A system is affected if it runs a Znuny version within the listed ranges AND has generated support bundles, which may contain unmasked passwords in the exported files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 7.1.6
Interim mitigation

Upgrade to Znuny version 7.1.5 or later. Until patched, avoid generating or sharing support bundles with untrusted parties, as they may contain unmasked passwords.

Recommended fix Moderate confidence

Znuny 7.1.5 or later (recommended: 7.1.6)

  1. 1. Identify the current Znuny installation version using the admin interface or command line tools.
  2. 2. For Znuny 6.0.x installations: Upgrade to the latest 6.0.x version available from Znuny (currently 6.0.48 has the vulnerability, check for newer patched release or migrate to a supported branch).
  3. 3. For Znuny 6.5.x installations: Upgrade to the latest 6.5.x version available from Znuny (currently 6.5.14 has the vulnerability, check for newer patched release or migrate to a supported branch).
  4. 4. For Znuny 7.0.x/7.1.x installations: Upgrade to version 7.1.5 or later (7.1.6 is the latest stable release).
  5. 5. After upgrade, verify the support bundle generation to confirm passwords are now properly masked.
  6. 6. Review the Znuny release notes for any additional security patches included in the upgrade.
Caveat Review Znuny upgrade guides; minor version upgrades within the same major series typically have minimal breaking changes, but test in staging first.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Znuny Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26847 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26847 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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