LiveActive security incident?Get immediate response
CVE Record

CVE-2022-46838: WordPress JS Help Desk plugin <= 2.7.1 - Unauthenticated Settings Change Vulnerability

Missing Authorization vulnerability in JS Help Desk JS Help Desk – Best Help Desk & Support Plugin allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects JS Help Desk – Best Help Desk & Support Plugin: from n/a through 2.7.1.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE affects the WordPress JS Help Desk plugin through version 2.7.1. An unauthenticated attacker may be able to change plugin settings because authorization checks are missing. The disclosed impact is high integrity and availability risk, not data theft. Public sources provided do not confirm active exploitation.

Executive priority

Treat this as urgent for any public WordPress site using JS Help Desk. The issue can affect site operations and configuration integrity without requiring an account. Prioritize inventory first, then remediation based on confirmed plugin presence and version.

Technical view

CVE-2022-46838 is a CWE-862 missing authorization issue in JS Help Desk, package js-support-ticket, through 2.7.1. CVSS 3.1 is 9.1: network exploitable, low complexity, no privileges, no user interaction, unchanged scope, no confidentiality impact, high integrity and availability impact.

Likely exposure

Internet-facing WordPress sites using JS Help Desk through version 2.7.1 are the primary exposure. Sites not running the plugin, or running versions outside the affected range, are not indicated as affected by the supplied sources.

Exploitation context

The CVSS vector indicates remote unauthenticated exploitation is plausible without user interaction. The source bundle says KEV is false, and no cited source confirms active exploitation, public exploit availability, or weaponized campaigns.

Researcher notes

Evidence is limited to the CVE record, CVE List entry, and Patchstack VDB reference. The sources identify missing authorization and settings-change impact but do not provide endpoint details, active exploitation evidence, or a specific fixed version in the supplied bundle.

Mitigation direction

  • Inventory WordPress sites for the js-support-ticket plugin.
  • Confirm whether JS Help Desk is version 2.7.1 or older.
  • Check vendor, CVE, and Patchstack guidance for confirmed remediation.
  • Prioritize update, removal, or disablement where business use is not required.
  • Monitor plugin settings for unauthorized changes until remediated.

Validation and detection

  • Verify installed plugin name and version from WordPress administration or asset inventory.
  • Flag any JS Help Desk version through 2.7.1 as potentially vulnerable.
  • Review recent plugin configuration changes for unexpected modifications.
  • Check web and WordPress logs for suspicious unauthenticated access patterns.
  • After remediation, confirm the version is no longer in the affected range.
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 · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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
cve · low confidence lookup

CVE-2022-46838 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
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

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
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H3.95.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2022-46838Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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 Desk – Best Help Desk & Support Pluginjs-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-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.