External risk intelligence

EASY-JS-WPAPI WordPress Plugin Credential Disclosure Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-115213

The vulnerability affects a WordPress plugin designed to interact with the WordPress REST API. WordPress sites are commonly deployed as public-facing web applications, and their REST API endpoints are frequently accessible via the internet, making this service surface likely to be exposed in standard deployments.

Authentication Bypass

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been identified in a WordPress plugin that handles administrator credentials. This issue allows unauthenticated attackers to gain full administrator access to affected websites by disclosing stored credentials and bypassing authentication.

  • Plugin exposes admin credentials to attackers.
  • Sites with public-facing APIs are at risk.
  • Confirm relevance and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker could gain administrative access to a WordPress site by exploiting a vulnerability in the EASY-JS-WPAPI Client HANDLE for the WordPress REST-API plugin. This vulnerability allows unauthenticated users to discover stored administrator credentials and bypass authentication checks, ultimately leading to full control over the website.

  • No authentication required to access.
  • Can obtain administrator credentials.
  • Leads to full site administrator access.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could expose administrator credentials stored by the WordPress REST-API plugin to unauthenticated users. When the plugin is used and its conditions for authentication verification are not met, an attacker could potentially gain full administrative control over the affected WordPress site.

  • Administrator credentials.
  • Unauthenticated access to credentials.
  • Full administrative access to site.

Operational Fix

Recommended remediation, mitigation, and detection steps

For this WordPress plugin vulnerability, application owners or the teams managing the WordPress deployment are likely responsible for remediation. The first practical step is to identify all instances of the plugin, confirm if they are internet-facing and business-critical, and then assign an owner to plan the appropriate response.

  • WordPress site owners should own the issue.
  • Verify internet exposure and business criticality.
  • 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 EASY-JS-WPAPI Client HANDLE plugin?

This software is a WordPress plugin designed to facilitate interaction between a site and the WordPress REST API. It is commonly used to manage communication or data exchange with the API; however, this specific component also performs credential handling, which is the primary source of the security risk.

What does CVE-2026-115213 mean for my security?

This vulnerability is classified as Improper Authentication (CWE-287). It means the plugin fails to verify who is making a request and improperly manages stored administrator credentials. Because of these flaws, a user without any valid login can trick the system into revealing sensitive account information, granting them full control over the website.

How can an attacker trigger this vulnerability?

An attacker triggers this by interacting with the WordPress REST API endpoints managed by the plugin. Because the flaw exists in the authentication logic itself, simply sending the right request allows the attacker to bypass access controls. Internal administrative actions within the WordPress dashboard do not trigger this, as the flaw specifically targets the exposed REST API interface.

Is my site at risk?

According to Halo Surface Signal, this risk is higher for standard WordPress deployments because they are typically public-facing. If your WordPress site exposes its REST API to the internet, it is likely reachable by an attacker. You should assume that any site with this plugin active and connected to the web has a significant surface for this threat.

How should I respond to this vulnerability?

Start by auditing your WordPress environment to find every instance where the EASY-JS-WPAPI Client HANDLE plugin is installed. Once identified, evaluate whether the site is critical and accessible from the internet. Prioritize these sites for immediate review and ensure you have assigned clear responsibility for managing the software configuration until a resolution is available.

References