GS JWT Authentication <= 1.0.0 - Unauthenticated SQL Injection
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- GS JWT Authentication for WP REST API
- Affected Version
<= 1.0.0- CVSS
- 7.5High
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-113615
At a glance
CVE-2026-113615 is a high-severity Improper Privilege Management vulnerability in the GS JWT Authentication for WP REST API WordPress plugin, affecting versions <= 1.0.0. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed November 2026, reported by Naoki Kawahigashi.
Vulnerability Overview
The GS JWT Authentication plugin for WordPress is vulnerable to SQL Injection in all versions up to, and including, 1.0.0. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-269: Improper Privilege Management
Reaching this weakness in GS JWT Authentication for WP REST API <= 1.0.0 takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. No fixed build of this plugin is recorded for GS JWT Authentication for WP REST API yet, so installs running <= 1.0.0 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C