External risk intelligence

GS JWT Authentication for WP REST API SQL Injection Allows Admin Session Takeover.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-113615

The vulnerability exists in a WordPress plugin that specifically modifies the REST API authentication mechanism. Because WordPress sites are typically public-facing web applications and the REST API is a core, internet-exposed feature, this vulnerability is directly reachable by unauthenticated users over the public internet.

SQL Injection

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This critical vulnerability affects a WordPress plugin that handles user authentication, potentially allowing unauthorized individuals to gain administrative access by exploiting a flaw in how data is processed within database queries. The primary concern is confirming whether this specific plugin is in use and, if so, understanding the extent of exposure.

  • Unauthenticated attackers can gain admin access.
  • Important for confirming plugin relevance and exposure.
  • Assess and mitigate if this plugin is active.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by sending a crafted request to unauthenticated REST API endpoints. The affected WordPress plugin does not properly handle a value within this request, allowing it to be inserted directly into a SQL query. This can lead to SQL injection, enabling the attacker to potentially steal sensitive data or hijack an administrator's session.

  • No user authentication required.
  • Crafting and sending a request to API endpoints.
  • SQL injection leading to admin session takeover.

Live Threat

Current exploitation, exposure, and threat context

Unauthenticated attackers could exploit this vulnerability to inject malicious SQL code into unpatched WordPress sites. This could allow them to gain administrator privileges and potentially access or modify sensitive website data, including user information and site content. The exposure occurs through unauthenticated REST API routes.

  • Sensitive WordPress data and administrator access.
  • SQL injection via unauthenticated REST routes.
  • Unauthorized access and data manipulation.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects the GS JWT Authentication for WP REST API WordPress plugin. The primary responsibility for addressing this issue likely lies with the application owner or the team managing the WordPress instance, as they are best positioned to identify and assess the impact of this plugin. The first practical step is to determine if this plugin is deployed, confirm its reachability from the internet, and ascertain its business criticality to prioritize remediation efforts.

  • WordPress application owners.
  • Verify plugin installation and internet exposure.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the GS JWT Authentication for WP REST API plugin?

This plugin is a tool for WordPress administrators to manage user authentication by issuing and verifying JSON Web Tokens (JWT) through the site's REST API. It acts as a bridge, allowing external services or front-end applications to interact securely with WordPress by replacing standard cookie-based logins with token-based access.

How does CVE-2026-113615 cause a security risk?

This vulnerability is a form of SQL injection, which falls under the CWE-269 weakness class regarding improper privilege management. It occurs because the plugin fails to clean input data before sending it to the database. By manipulating these inputs, an attacker can trick the system into granting them administrative privileges or accessing session information they should not have.

Does this vulnerability require me to be logged in?

No. The flaw exists within unauthenticated REST API routes, meaning an attacker does not need an account or special credentials to trigger it. Conversely, if your site's configuration blocks access to the REST API entirely, or if you are using specific security rules that filter incoming request parameters before they reach the plugin, the attack path may be disrupted.

Is my site at risk if it uses this plugin?

According to Halo Surface Signal, this vulnerability is highly relevant because the plugin modifies core REST API authentication, a feature that is typically exposed to the public internet for web functionality. If your WordPress site is reachable by the public, this component is directly exposed, making the site a potential target for unauthenticated attackers.

What steps should I take if I use this software?

Begin by auditing your active WordPress plugins to see if this specific version is installed. If it is present, prioritize assessing your site's reliance on it for authentication. Since the vulnerability allows for full administrative takeover, you should immediately consider disabling or removing the plugin while you investigate available security updates or alternative authentication methods.

References