Safeguard
Vulnerability Analysis•

CVE-2022-46839: Critical File Upload Flaw in JS Help Desk Plugin

CVE-2022-46839 is a critical (10.0) unrestricted file upload flaw in the JS Help Desk WordPress plugin through 2.7.1. Update or remove it right away.

Safeguard Security Team
3 min read

CVE-2022-46839 is a critical (CVSS 10.0) unrestricted file upload flaw in the JS Help Desk WordPress plugin, versions through 2.7.1. It needs no login. I could not confirm the fixed version, so update to the latest release and treat any site that ran 2.7.1 or earlier as suspect.

What's affected

The record lists JS Help Desk, Best Help Desk and Support Plugin, from the earliest release through 2.7.1. The Patchstack page cited in the record is titled for an arbitrary file upload in version 2.7.1, but I could not load its details, so the patched version is unconfirmed.

The NVD record was published on 5 January 2024. The vector is network, low complexity, no privileges, no interaction, with changed scope, which is the maximum severity profile in CVSS.

How to check if you're exposed

In the WordPress admin, open Plugins and read the version shown under JS Help Desk. With WP-CLI you can run wp plugin list --fields=name,status,version and look for the entry. Check inactive plugins too, since a deactivated plugin still sits on disk.

What to do now

  1. Update JS Help Desk to the latest release from the plugin directory, and confirm the version is newer than 2.7.1.
  2. If an update is not available yet, deactivate and delete the plugin, or restrict access to it while you wait. Do not leave a vulnerable copy installed but switched off.
  3. Review your site for changes you did not make, such as new accounts, altered content or unexpected files, and rotate credentials if anything looks wrong.
  4. Add the plugin to your inventory so the next advisory for it reaches you without a manual search.

Why it matters

CWE-434 is unrestricted upload of a file with a dangerous type. A help desk plugin accepts attachments from visitors, so it has an upload path that is reachable without an account. If the server accepts a file type that it can then run, an upload becomes code execution on the web host.

That is why the score reaches 10.0. A help desk is also an ideal place for this class of bug because the whole purpose of the page is to take files from strangers. KEV is false and I found no advisory that reports exploitation, but the combination of no login and a public form makes prompt action sensible. After updating, look in the uploads directory for files with script extensions.

Quick check

Does an attacker need an account?

No. The record's vector requires no privileges and no user interaction.

What should I check after updating?

Look for unexpected script files in the WordPress uploads folder and for accounts you did not create.

Sources

You can also run the free in-browser dependency scan at gold.safeguard.sh/scan to see which known vulnerabilities your dependencies carry.

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.