WsdeskWordPress extension · Elula
CVE-2025-47658
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in ELEXtensions ELEX WordPress HelpDesk & Customer Ticketing System elex-helpdesk-customer-support-ticket-system allows Upload a Web Shell to a Web Server.This issue affects ELEX WordPress HelpDesk & Customer Ticketing System: from n/a through <= 3.2.9.
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 confidenceThe ELEX WordPress HelpDesk plugin versions 3.2.9 and below contain an unrestricted file upload vulnerability allowing authenticated attackers to upload malicious web shells to the server, potentially achieving remote code execution and full system compromise.
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
< 3.3.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and look for 'ELEX WordPress HelpDesk' or 'Wsdesk' plugin. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header for 'Version:' comment, or inspect the /wp-content/plugins/ directory for the plugin folder and read its main file.Affected if The installed version is 3.2.9 or lower (less than 3.3.0)
-
Verify file upload functionality is accessibleCheck if the helpdesk ticket system allows file attachments. Look for upload forms in the ticket submission or response pages. Inspect the plugin's AJAX endpoints or REST API routes that handle file uploads by reviewing the plugin PHP files for 'wp_handle_upload' or 'move_uploaded_file' functions.Affected if The upload functionality is enabled and accessible to authenticated users (any logged-in user)
-
Inspect uploads directory for suspicious filesCheck the WordPress uploads folder (typically /wp-content/uploads/) for recently added PHP files, especially in subdirectories with random names. Use file system commands: 'find /wp-content/uploads -name "*.php" -mtime -30' to find recently modified PHP files.Affected if Any PHP files exist in the uploads directory that were not intentionally placed there by administrators
-
Review recent file modifications in plugin directoryRun 'find /wp-content/plugins/ -name "*.php" -mtime -30' to detect recently added or modified PHP files. Check for unknown files or backdoors in the plugin folder, especially files with names like 'shell.php', 'backdoor.php', or base64-encoded scripts.Affected if Unexpected PHP files exist in the plugin directory or any web-accessible directory with recent modification dates
You are affected if the ELEX/Wsdesk plugin version is 3.2.9 or below AND the ticket attachment feature is active, as this allows authenticated users to upload executable files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.3.0
Update the plugin to the latest version if a patch is available, or implement web application firewall rules and server-side file type validation to block PHP uploads; remove any suspected malicious files and audit for existing compromise.
3.3.0
- Backup your WordPress site database and files before making any changes
- Navigate to WordPress Admin Dashboard > Plugins > Installed Plugins
- Locate 'Wsdesk' (ELEX WordPress HelpDesk & Customer Ticketing System) in the plugin list
- Click 'Update now' if an update is available, or manually download version 3.3.0 from the WordPress plugin repository and upload it
- Verify the plugin version after update confirms 3.3.0
- Test the file upload functionality to ensure legitimate file types are still accepted while malicious files are blocked
- Clear any server-side caches if applicable
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wsdesk
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47658 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47658 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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