Skip to main content
Mallory
HighVulnerability

CVE-2026-32534: Blind SQL Injection in JoomSky JS Help Desk <= 3.0.3

Published Mar 25, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.5High · v3.1
EPSS0.23%14th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-32534CWE-89 · Improper Neutralization of Special…

CVE-2026-32534 is a blind SQL injection vulnerability in the JoomSky JS Help Desk WordPress plugin (js-support-ticket) affecting versions up to and including 3.0.3. The issue is caused by improper neutralization of special elements used in SQL commands, allowing attacker-controlled input to influence backend database queries. The available information identifies the flaw as blind SQL injection, indicating that exploitation does not directly return query results but can still permit inference of database content through application behavior or timing differences.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an attacker with low privileges to execute blind SQL injection against the application's backend database. Based on the provided CVSS vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L), the primary impact is high confidentiality loss through unauthorized extraction of database-resident information, with limited availability impact. No direct integrity impact is indicated in the provided data.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to the vulnerable plugin functionality to only trusted users, minimize the number of accounts with access to JS Help Desk features, and monitor for anomalous requests targeting plugin parameters. Deploy or tune a WAF/virtual patching ruleset to detect and block SQL injection payloads against JS Help Desk endpoints where feasible. Review database permissions used by the application and ensure the WordPress/database account operates with least privilege to reduce exposure.

Remediation

Patch, then assume compromise.

Upgrade JoomSky JS Help Desk (js-support-ticket) to a version newer than 3.0.3 if a fixed release is available from the vendor. The vulnerable code path should be remediated by using parameterized queries/prepared statements, strict server-side input validation, and safe database APIs that prevent attacker-controlled input from being concatenated into SQL statements. If vendor guidance or a patched version is published, follow that advisory.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-32534 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-32534 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-32534?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-32534.
Is there a patch for CVE-2026-32534?
Upgrade JoomSky JS Help Desk (js-support-ticket) to a version newer than 3.0.3 if a fixed release is available from the vendor. The vulnerable code path should be remediated by using parameterized queries/prepared statements, strict server-side input validation, and safe database APIs that prevent attacker-controlled input from being concatenated into SQL statements.
How severe is CVE-2026-32534?
CVE-2026-32534 has a CVSS v3.1 score of 8.5 (High) and an EPSS score of 0.23% (14th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.