CVE-2022-46839

JS Help Desk <= 2.7.1 - Unauthenticated Arbitrary File Upload

2023-01-27 00:00
R3N0

Strategic Overview

Status
Patched in 2.7.2
Affected Plugin
JS Help Desk – AI-Powered Support & Ticketing System
Affected Version
<= 2.7.1
CVSS
9.8Critical
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2022-46839
View all JS Help Desk – AI-Powered Support & Ticketing System vulnerabilities

At a glance

CVE-2022-46839 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the JS Help Desk WordPress plugin, affecting versions <= 2.7.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.7.2; sites on affected versions should update now. Disclosed January 2023, reported by R3N0.

Vulnerability Overview

The JS Help Desk plugin for WordPress is vulnerable to arbitrary file uploads in versions up to, and including, 2.7.1. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected sites server which may make remote code execution possible.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in JS Help Desk <= 2.7.1 takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For JS Help Desk the fix is 2.7.2: builds <= 2.7.1 are affected, anything from 2.7.2 onward is not.

Remediation

Update to version 2.7.2, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: JS Help Desk 2.7.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2022-46839https://www.wordfence.com/threat-intel/vulnerabilities/id/65e2e9e3-2778-4baf-8269-fc13d5ef1212https://nvd.nist.gov/vuln/detail/CVE-2022-46839

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C