Unauthenticated database disclosure via cookie SQL injection
Published Mar 4, 2026 · Updated Mar 4, 2026
SQL injection in the JS Help Desk WordPress plugin 2.8.2 and earlier allows remote attackers to read database data through a crafted cookie. The remaining SQL-query sink insufficiently escapes the js-support-ticket-token-tkstatus cookie and incorporates it into an existing query without sufficient preparation. No authentication or user interaction is required; injected clauses can expose sensitive database information, while integrity and availability impacts are not reported.
Summary
What happened
SQL injection in the JS Help Desk WordPress plugin 2.8.2 and earlier allows remote attackers to read database data through a crafted cookie. The remaining SQL-query sink insufficiently escapes the js-support-ticket-token-tkstatus cookie and incorporates it into an existing query without sufficient preparation. No authentication or user interaction is required; injected clauses can expose sensitive database information, while integrity and availability impacts are not reported.
The record
- CVE
- CVE-2023-7337
- Published
- Mar 4, 2026
- Updated
- Mar 4, 2026
- Vendor
- JoomSky
- Product
- JS Help Desk
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 4, 2026CVE publishedPublication date reported by the CVE source.
- Mar 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=2.8.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo