dbcve.org
WsdeskWordPress extension · Elula

CVE-2025-13534

HIGH · 8.8 CVSS v3.1 Published 2025-12-02
Fix available
A fix is available. Upgrade to 3.3.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
The ELEX WordPress HelpDesk & Customer Ticketing System plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.3.2. This is due to missing authorization checks on the eh_crm_edit_agent AJAX action. This makes it possible for authenticated attackers, with Contributor-level access and above, to escalate their WSDesk privileges from limited "Reply Tickets" permissions to full helpdesk administrator capabilities, gaining unauthorized access to ticket management, settings configuration, agent administration, and sensitive customer data.

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

The ELEX WordPress HelpDesk plugin lacks authorization validation on the eh_crm_edit_agent AJAX endpoint, allowing any authenticated user with Contributor-level permissions or higher to modify their own agent privileges. This enables attackers to escalate from limited ticket reply capabilities to full helpdesk administrator access, exposing sensitive customer data and system configuration.

MitigationUpdate the ELEX WordPress HelpDesk plugin to version 3.3.3 or later which contains the authorization fix. If immediate patching is not possible, disable the eh_crm_edit_agent AJAX action via wp_ajax_nopriv hooks or implement temporary access controls at the web server level.

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
WsdeskWordPress extension
Affected:< 3.3.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Check installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > look for 'ELEX WordPress HelpDesk' or 'Wsdesk' and note the version number displayed
    Affected if Version is lower than 3.3.3 or the version is not displayed (indicating an old/unpatched release)
  2. Verify eh_crm_edit_agent AJAX endpoint exists
    Check the plugin files for registered AJAX actions. In the main plugin PHP file, look for add_action('wp_ajax_eh_crm_edit_agent', ...) or add_action('wp_ajax_nopriv_eh_crm_edit_agent', ...)
    Affected if The eh_crm_edit_agent action is registered without proper capability checks (such as 'manage_options' or 'edit_users')
  3. Inspect the callback function for authorization logic
    Locate the function handling eh_crm_edit_agent (usually in includes/class-*.php or similar) and review the code for current_user_can() or role verification before allowing privilege modifications
    Affected if The function allows any authenticated user (Contributor level or higher) to modify their own agent role without elevated permission checks
  4. Confirm WordPress user roles present
    In WordPress admin > Users > Roles, check if Contributor or higher roles exist and have access to the helpdesk functionality
    Affected if Users with Contributor role or above exist and can access the WordPress dashboard (the vulnerability requires any authenticated user with Contributor-level permissions)

Your environment is affected if the ELEX WordPress HelpDesk plugin version is below 3.3.3 AND the eh_crm_edit_agent AJAX endpoint is accessible to users without elevated admin privileges.

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 3.3.3 or later
Fixed in 3.3.3
Interim mitigation

Update the ELEX WordPress HelpDesk plugin to version 3.3.3 or later which contains the authorization fix. If immediate patching is not possible, disable the eh_crm_edit_agent AJAX action via wp_ajax_nopriv hooks or implement temporary access controls at the web server level.

Recommended fix High confidence

Wsdesk 3.3.3

  1. Update the Wsdesk (ELEX WordPress HelpDesk & Customer Ticketing System) plugin to version 3.3.3 or later via the WordPress plugin admin dashboard, or replace the plugin files with the updated version.

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

Fix this in Wsdesk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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