dbcve.org
ZnunyApplication

CVE-2025-43926

MEDIUM · 6.1 CVSS v3.1 Published 2025-05-08
Fix available
A fix is available. Upgrade to after 7.1.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 through 6.5.14 and 7.x through 7.1.6. Custom AJAX calls to the AgentPreferences UpdateAJAX subaction can be used to set user preferences with arbitrary keys. When fetching user data via GetUserData, these keys and values are retrieved and given as a whole to other function calls, which then might use these keys/values to affect permissions or other settings.

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 confidence

Znuny allows authenticated users to inject arbitrary keys into user preferences via the AgentPreferences UpdateAJAX subaction. These user-controlled keys are later retrieved by GetUserData and passed to other functions that may use them to modify permissions or security settings, leading to potential privilege escalation.

MitigationImplement strict allow-list validation for preference keys in UpdateAJAX and sanitize/validate preference keys before they are used in functions that affect permissions or security settings.

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.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Identify Znuny version
    Locate the Znuny installation and check the version file or package version. Common locations include /opt/znuny or checking the RPM/DEB package version.
    Affected if Version is <= 6.5.14 or >= 7.0.1 and <= 7.1.6
  2. Confirm AgentPreferences module access
    Verify that authenticated agents have access to the AgentPreferences module in the system configuration. Check Admin > Group > Role permissions for the AgentPreferences module.
    Affected if Authenticated users have write access to AgentPreferences
  3. Check UpdateAJAX availability
    Inspect the AgentPreferences controller or module to confirm the UpdateAJAX subaction exists and is accessible to authenticated users without strict key validation.
    Affected if UpdateAJAX subaction accepts arbitrary preference keys without allow-list validation
  4. Identify user preference storage
    Locate where user preferences are stored (database table or config file) and check if the GetUserData function retrieves custom keys that could affect security settings.
    Affected if GetUserData retrieves and uses custom preference keys in permission or security-related functions

User is affected if running a Znuny version <= 6.5.14 or between 7.0.1 and 7.1.6 AND authenticated agents can access the AgentPreferences UpdateAJAX subaction without strict key allow-listing.

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

Implement strict allow-list validation for preference keys in UpdateAJAX and sanitize/validate preference keys before they are used in functions that affect permissions or security settings.

Recommended fix Moderate confidence

Znuny 6.5.15+ or Znuny 7.1.7+ (depending on your major version)

  1. 1. Identify the currently installed Znuny version by checking the admin interface or package management system
  2. 2. For Znuny 6.x installations: Plan upgrade to Znuny 6.5.15 or later
  3. 3. For Znuny 7.x installations: Plan upgrade to Znuny 7.1.7 or later
  4. 4. Before upgrading, backup the Znuny database and configuration files
  5. 5. Review the Znuny upgrade documentation for your specific version
  6. 6. Perform the upgrade following standard Znuny upgrade procedures
  7. 7. After upgrade, verify that the AgentPreferences AJAX functionality works correctly
  8. 8. Test that user preferences can only be set for allowed/predefined keys
Caveat Review Znuny release notes for any breaking changes between your current version and the target upgrade version before proceeding

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

Fix this in Znuny Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43926 — 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-43926 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