CVE-2023-23679

JS Help Desk – Best Help Desk & Support Plugin <= 2.7.7 - Authenticated (Subscriber+) Insecure Direct Object Reference

2023-06-20 00:00
Fariq Fadillah Gusti Insani (fariqfgi)

Strategic Overview

Status
Patched in 2.7.8
Affected Plugin
JS Help Desk – AI-Powered Support & Ticketing System
Affected Version
<= 2.7.7
CVSS
6.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-23679
View all JS Help Desk – AI-Powered Support & Ticketing System vulnerabilities

At a glance

CVE-2023-23679 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the JS Help Desk WordPress plugin, affecting versions <= 2.7.7. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.7.8; sites on affected versions should update now. Disclosed June 2023, reported by Fariq Fadillah Gusti Insani (fariqfgi).

Vulnerability Overview

The "JS Help Desk – Best Help Desk & Support Plugin" plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 2.7.7 via the 'email' parameter due to missing validation on a user controlled key. This can allow authenticated attackers, with subscriber-level access and above, to delete help desk tickets.

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 interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

JS Help Desk <= 2.7.7 carries this weakness at email, and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For JS Help Desk the fix is 2.7.8: builds <= 2.7.7 are affected, anything from 2.7.8 onward is not.

Remediation

Update to version 2.7.8, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: JS Help Desk 2.7.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-23679https://www.wordfence.com/threat-intel/vulnerabilities/id/962af7eb-b2eb-4190-bf0d-cb05cb28f10bhttps://nvd.nist.gov/vuln/detail/CVE-2023-23679

Related records

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