Cyber Resilience

CVE-2025-11456

Elula Wsdesk ≤ 3.3.2

Published
21 November 2025
Modified
26 November 2025
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0073 52th percentile
Risk Priority 72 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-11456 is a critical-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Elula Wsdesk. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-3 (Malicious Code Protection) and CM-7 (Least Functionality) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-11456 is an arbitrary file upload vulnerability in the ELEX WordPress HelpDesk & Customer Ticketing System plugin for WordPress, affecting all versions up to and including 3.3.1. The flaw stems from missing file type validation in the eh_crm_new_ticket_post() function, enabling attackers to upload arbitrary files to the affected site's server. It is classified under CWE-434 and carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating critical severity.

Unauthenticated attackers can exploit this vulnerability remotely with low complexity and no user interaction required. By leveraging the flawed ticket submission function, they can upload malicious files, such as web shells, potentially leading to remote code execution on the server.

Advisories and references, including Wordfence threat intelligence and WordPress plugin repository sources, point to the vulnerable code in class-crm-ajax-functions-three.php and a related changeset (3399391). Mitigation involves updating the plugin to a patched version beyond 3.3.1, as indicated by the version scope in the CVE description.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1505 Server Software Component Persistence
Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems.
T1505.003 Web Shell Persistence
Adversaries may backdoor web servers with web shells to establish persistent access to systems.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1105 Ingress Tool Transfer Command And Control
Adversaries may transfer tools or other files from an external system into a compromised environment.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-47658Same product: Elula Wsdesk
CVE-2025-10039Same product: Elula Wsdesk
CVE-2025-12022Same product: Elula Wsdesk
CVE-2025-12023Same product: Elula Wsdesk
CVE-2025-12169Same product: Elula Wsdesk
CVE-2024-12171Same product: Elula Wsdesk
CVE-2025-10054Same product: Elula Wsdesk
CVE-2025-12085Same product: Elula Wsdesk
CVE-2025-13534Same product: Elula Wsdesk
CVE-2024-24714Shared CWE-434

Affected Assets

elula
wsdesk
≤ 3.3.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.1.1

Mitigating Controls (NIST 800-53 r5) AI

Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.

Least functionality restricts the file types and automatic processing capabilities the system will accept.

SC-18 Mobile Code partial match

Mobile-code controls define, authorize, and block unacceptable uploaded code before automatic processing occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-05 mostly match
prevents

Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.

PR.PS-01 partial match
prevents

Hardened configuration baselines can enforce allowed file types and processing rules.

PR.PS-06 partial match
prevents

Secure development practices include input validation and file-type restrictions that prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Configuration and acceptance testing verify that file-upload handling enforces allowed types and does not permit dangerous content to be stored or executed.

prevents

Secure-coding guidelines and security testing explicitly address restrictions on allowed file types and upload handling, reducing the risk that dangerous file uploads are accepted without validation.

prevents

Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.

mitigates

Application allow-listing and pre-use scanning of received files directly blocks the introduction of executable content that has not been vetted, eliminating the primary vector for unrestricted dangerous file uploads.

References