JS Help Desk

JS Help Desk before 3.1.5 loads a requested support ticket without confirming that the authenticated requester owns it. A low-privileged user can supply another user's ticket identifier and receive the ticket's subject, message body and reporter personally identifiable information. The published.

JS Help Desk before 3.1.4 grants a support-agent capability to the WordPress Contributor role during activation, then exposes a user-listing handler without an additional capability check. A Contributor can invoke that handler and enumerate the email addresses of all registered WordPress users. The published.

JS Help Desk before 3.1.4 exposes a front-end request dispatcher without authentication, a nonce check or ticket-ownership validation. An unauthenticated visitor can submit a file accepted by the plugin and select another user's support ticket as its destination, causing the file to be stored and attached to that ticket. The plugin limits uploads to its inert allowed extensions, so the published record does not establish executable-file upload, but the operation can tamper with support records and place attacker content in a trusted workflow.

JS Help Desk before 3.1.4 updates a selected support-ticket reply without verifying that the authenticated requester owns that reply or its ticket. Any Subscriber-or-higher user can submit another reply's identifier and replacement content, overwriting messages across the support system. The published.

JS Help Desk before 3.1.4 returns support-ticket content through a nonce-gated search handler without an authorization or ownership check. Any authenticated Subscriber-or-higher user who can obtain the nonce can search or select other users' tickets and read their subjects and full message bodies. The published.

JS Help Desk is affected by filesystem traversal. Exposure depends on how the affected operation is made reachable by the site. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.

JS Help Desk is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.

JS Help Desk is affected by filesystem traversal. Exposure depends on how the affected operation is made reachable by the site. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.

JS Help Desk is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

JS Help Desk is affected by filesystem traversal. Exposure depends on how the affected operation is made reachable by the site. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.

JS Help Desk – Best Help Desk & Support Plugin is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

JS Help Desk – Best Help Desk & Support Plugin is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

JS Help Desk is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.