LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32535: WordPress JS Help Desk plugin <= 3.0.3 - Insecure Direct Object References (IDOR) vulnerability

Authorization Bypass Through User-Controlled Key vulnerability in JoomSky JS Help Desk js-support-ticket allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects JS Help Desk: from n/a through <= 3.0.3.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32535 affects the WordPress JS Help Desk plugin through version 3.0.3. A logged-in user may be able to access help desk data they should not see because the plugin relies on user-controlled identifiers without proper authorization checks.

Executive priority

Treat as a moderate-priority data exposure risk. Prioritize sites using this help desk plugin where customer, employee, or support ticket data may be sensitive, especially public-facing WordPress portals with many registered users.

Technical view

This is an IDOR/authorization bypass issue in JoomSky JS Help Desk, package js-support-ticket, mapped to CWE-639. CVSS 3.1 is 6.5: network exploitable, low complexity, low privileges, no user interaction, high confidentiality impact, no integrity or availability impact reported.

Likely exposure

Exposure is likely limited to WordPress sites running JS Help Desk through version 3.0.3, especially where untrusted or lower-privileged users can log in. The sources do not identify affected configurations beyond the plugin and version range.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The vulnerability requires a logged-in attacker and appears focused on unauthorized data access, not code execution or site takeover.

Researcher notes

Available public detail is limited. The CVE describes user-controlled key authorization bypass in access control levels, but does not provide endpoint details, proof of concept, or a named fixed version in the supplied bundle.

Mitigation direction

  • Identify WordPress sites using the JS Help Desk plugin.
  • Check whether js-support-ticket is version 3.0.3 or earlier.
  • Review vendor and Patchstack guidance for a fixed version or official workaround.
  • If no fix is available, consider disabling the plugin until guidance is published.
  • Restrict plugin access to trusted users where business operations allow.

Validation and detection

  • Confirm plugin name, package, and version in WordPress asset inventory.
  • Review help desk user roles for unnecessary low-privilege access.
  • Test authorization boundaries in a non-production environment only.
  • Review logs for unusual access to tickets or support records by low-privilege users.
  • Monitor CVE and Patchstack entries for updated remediation details.
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-2026-32535 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
6.5 (3.1)
Known Exploited
No
Published

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

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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-32535Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
JoomSkyJS 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.