dbcve.org
WsdeskWordPress extension · Elula

CVE-2025-11456

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-21
Fix available
A fix is available. Upgrade to 3.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 arbitrary file uploads due to missing file type validation in the eh_crm_new_ticket_post() function in all versions up to, and including, 3.3.1. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 versions up to 3.3.1 lack file type validation in the eh_crm_new_ticket_post() function, allowing unauthenticated attackers to upload arbitrary files to the server. This can lead to remote code execution if executable files (e.g., PHP scripts) are uploaded and accessed.

MitigationImmediately update the plugin to version 3.3.2 or later which contains the fix, or disable the plugin until patching is possible. Review server access logs for suspicious file uploads and remove any malicious files already uploaded.

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.2

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
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 checks

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

  1. Locate the Elula Wsdesk plugin
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Wsdesk' or 'HelpDesk' by Elula. Note the version number displayed below the plugin name.
    Affected if The plugin is installed and the version shown is below 3.3.2 (e.g., 3.3.1, 3.3.0, etc.)
  2. Verify plugin status
    Confirm in the Plugins page whether the Wsdesk plugin is currently activated. A green underline or 'Active' status means the plugin is running.
    Affected if The plugin is activated - the vulnerability is only exploitable when the plugin is running.
  3. Check ticket attachment capability
    Navigate to the plugin settings (Wsdesk > Settings > Tickets > General or similar attachment configuration). Look for an option enabling file attachments on tickets.
    Affected if File attachments are enabled - this feature must be active for the upload vulnerability to be reachable.
  4. Inspect upload configuration
    In WordPress admin, go to Media > Settings (or Wsdesk settings) and check if there are restrictions on allowed file types for ticket attachments. If no explicit whitelist exists, arbitrary files may be accepted.
    Affected if No file type whitelist is configured or enforced for ticket attachments.

You are affected if the Wsdesk plugin version is below 3.3.2, the plugin is active, and the ticket attachment feature is enabled.

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.2 or later
Fixed in 3.3.2
Vendor patch plugins.trac.wordpress.org →
Interim mitigation

Immediately update the plugin to version 3.3.2 or later which contains the fix, or disable the plugin until patching is possible. Review server access logs for suspicious file uploads and remove any malicious files already uploaded.

Recommended fix High confidence

3.3.2

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the ELEX WordPress HelpDesk & Customer Ticketing System (Wsdesk) plugin.
  4. 4. If an update to version 3.3.2 is available, click 'Update Now' to install the patched version.
  5. 5. Alternatively, download version 3.3.2 from the WordPress Plugin Repository and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is running version 3.3.2 under Plugins > Installed Plugins.

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

Fix this in Wsdesk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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