LiveActive security incident?Get immediate response
CVE Record

CVE-2023-23679: WordPress JS Help Desk – Best Help Desk & Support Plugin Plugin <= 2.7.7 is vulnerable to Insecure Direct Object References (IDOR)

Authorization Bypass Through User-Controlled Key vulnerability in JS Help Desk js-support-ticket allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects JS Help Desk: from n/a through 2.7.7.

MediumCVSS 4.6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-23679 affects the WordPress JS Help Desk plugin through version 2.7.7. A logged-in user may be able to access an action not properly restricted by permissions, with Patchstack describing ticket deletion impact. This is not a full site takeover based on the supplied CVSS, but it can affect support operations and ticket integrity.

Executive priority

Treat this as a moderate operational-risk item. Prioritize externally reachable WordPress sites that use JS Help Desk for customer support, especially where many non-admin users have accounts. Address during the next vulnerability remediation cycle unless local evidence shows suspicious ticket deletion.

Technical view

The issue is an IDOR/authorization bypass weakness, mapped to CWE-639, in js-support-ticket. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L, indicating remote reachability, low attack complexity, required login, user interaction, and limited integrity and availability impact.

Likely exposure

Exposure is most likely on WordPress sites with JS Help Desk installed at version 2.7.7 or earlier. Sites without the plugin, or with versions outside the affected range, are not indicated as affected in the supplied bundle.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability requires privileges and user interaction according to CVSS, reducing urgency compared with unauthenticated flaws, but support-ticket deletion could still disrupt customer support records.

Researcher notes

Evidence is limited to the CVE record and Patchstack reference. The bundle identifies IDOR leading to ticket deletion but does not provide a fixed version, exploit proof, or active exploitation evidence. Validate authorization boundaries around ticket actions without relying on offensive reproduction steps.

Mitigation direction

  • Inventory WordPress sites for the JS Help Desk plugin and installed version.
  • If version is 2.7.7 or earlier, check vendor and Patchstack guidance for remediation.
  • Update, disable, or remove the plugin according to confirmed vendor guidance.
  • Limit WordPress accounts with access to help desk functionality.
  • Back up ticket data before remediation where operationally appropriate.

Validation and detection

  • Confirm whether js-support-ticket is installed on each WordPress instance.
  • Verify the installed plugin version against the affected range through 2.7.7.
  • Review support-ticket audit logs for unexpected deletions or permission anomalies.
  • Confirm remediation by documenting the updated, disabled, or removed plugin state.
  • Recheck exposed WordPress sites after remediation for the affected plugin version.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-23679 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.6CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L2.12.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.6Medium
CVSS 3.1 vector shape for CVE-2023-23679Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
JS Help DeskJS Help Deskjs-support-ticket, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.