What is the CVSS score of CVE-2026-14931?

CVE-2026-14931 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.1%.

Is there a public PoC exploit available for CVE-2026-14931?

Yes, a public proof-of-concept exploit is available for CVE-2026-14931. Prioritise patching immediately. EPSS: 0.1%.

Is there a patch available for CVE-2026-14931?

Yes, a patch is available for CVE-2026-14931. Update the affected software to the latest version immediately.

JS Help Desk CVE-2026-14931

EUVD-2026-51424 MEDIUM

Information Exposure (CWE-200)

2026-07-31 WPScan

GHSA-4w98-gcq5-58rp

WordPress Information Disclosure Js Help Desk Unknown

6.5

CVSS 3.1 · Vendor: WPScan

Severity by source

Vendor (WPScan) PRIMARY

6.5 MEDIUM

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

vuln.today AI

6.5 MEDIUM

PR:L reflects required Contributor account; C:H for full user email roster exposure; I:N and A:N as no write or availability impact exists.

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

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 31, 2026 - 20:29 vuln.today

CVSS changed

Jul 31, 2026 - 20:22 NVD

6.5 (MEDIUM)

Patch available

Jul 31, 2026 - 07:01 EUVD

CVE Published

Jul 31, 2026 - 06:00 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 31, 2026 - 06:00 cve.org

MEDIUM 6.5

DescriptionCVE.org

The JS Help Desk WordPress plugin before 3.1.4 grants a support-agent capability to the Contributor role on activation and does not perform a capability check on a user-listing handler, allowing Contributor-level users to enumerate the email addresses of all registered WordPress users.

AnalysisAI

User email enumeration in the JS Help Desk WordPress plugin (versions before 3.1.4) allows any Contributor-level site user to harvest the email addresses of all registered WordPress users. Two design flaws compound: the plugin unconditionally grants a support-agent capability to the built-in Contributor role at activation time, and the user-listing handler omits any capability check entirely, making the Contributor elevation the effective attack precondition. A public proof-of-concept is documented by WPScan; however, EPSS places exploitation probability at 0.14% (4th percentile), indicating no public exploit is currently being run at scale. No CISA KEV listing is present.

Technical ContextAI

The vulnerability stems from two interacting failures in WordPress's role and capability management system (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor). WordPress enforces access control through a capability model where roles (Subscriber, Contributor, Author, Editor, Administrator) each carry specific capabilities checked via current_user_can(). The JS Help Desk plugin (CPE: cpe:2.3:a:unknown:js_help_desk:*:*:*:*:*:*:*:*) violates this model in two ways: first, it programmatically adds its custom 'support-agent' capability to the Contributor role during plugin activation - a persistent side-effect that remains after the activation hook fires; second, its user-listing AJAX or REST handler performs no current_user_can() check, meaning any user whose role includes the support-agent capability (i.e., all Contributors after activation) can invoke it freely. The result is complete enumeration of all user_email values stored in the wp_users table. Reported by WPScan under EUVD-2026-51424.

RemediationAI

Update the JS Help Desk WordPress plugin to version 3.1.4 or later, which is the vendor-released patch addressing both the improper support-agent capability grant at activation and the missing capability check on the user-listing handler. Patch availability is confirmed by vendor per the WPScan advisory (https://wpscan.com/vulnerability/852375ba-b8f5-4fef-8a37-d889d97227f0/). An exact fix-version commit or changelog was not independently verifiable from the available references beyond the '<3.1.4' boundary. As an interim compensating control before patching, administrators should restrict Contributor role assignments to trusted internal users only and disable open user registration (Settings > General > 'Anyone can register'). Note that simply deactivating the plugin does NOT revoke the support-agent capability already added to the Contributor role - administrators should use a capability management plugin (e.g., Members or User Role Editor) to manually remove the support-agent capability from Contributors, or reactivate the patched version to allow it to correct the role configuration on activation.