External risk intelligence

Chargely Free Subscriptions For Woocommerce WordPress Plugin Information Disclosure Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-116528

The vulnerability affects a WordPress plugin designed for public-facing e-commerce websites. The REST API endpoint is public by default in standard WordPress deployments, making it accessible over the internet to unauthenticated users without requiring specific configurations.

Information Disclosure

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

A critical vulnerability has been identified in the Chargely Free Subscriptions For WooCommerce WordPress plugin. This issue allows unauthenticated attackers to access sensitive configuration details, specifically your WooCommerce REST API consumer key and secret. Possession of these credentials grants unauthorized read and write access to your entire online store.

  • Unauthenticated access to store credentials.
  • Exposes critical e-commerce data.
  • Confirm plugin relevance and scope.

Attack Path

How an attacker could exploit the issue

An attacker can access a public API endpoint on a WooCommerce store to steal the store's API credentials. This allows them to then perform actions on the store, such as reading or writing data.

  • Unauthenticated access to a public API.
  • Retrieving stored API consumer key and secret.
  • Full store read and write access.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could expose sensitive WooCommerce store credentials, specifically the consumer key and secret for the REST API. An unauthenticated attacker could access this information, potentially leading to unauthorized modifications or data exfiltration from the e-commerce store.

  • Store API credentials at risk.
  • Unauthenticated REST API access.
  • Unauthorized store access and data compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

To address this vulnerability, the e-commerce platform or website owner, likely supported by their web development or infrastructure team, must first identify all instances of the affected plugin. Subsequently, they should determine the exposure and business criticality of each instance to prioritize remediation efforts. This involves confirming whether the plugin's API endpoint is accessible externally and if the online store is actively using it. Once the accountable owner is identified, a plan for remediation, which may involve vendor coordination or applying available fixes, should be executed based on the assessed risk.

  • Ownership: E-commerce platform or website owner.
  • Verify first: External reachability of the plugin's API.
  • Action: Plan and execute remediation based on 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 Chargely Free Subscriptions For WooCommerce plugin?

This WordPress plugin is an e-commerce tool used to manage recurring billing and subscription services within WooCommerce stores. It integrates site functionality with the Chargely payment platform, storing necessary API credentials to process transactions and handle subscription data.

What does CVE-2026-116528 mean for data security?

It is an Information Exposure vulnerability (CWE-200). The plugin fails to verify user permissions for a specific REST API route, effectively making sensitive data public. Because the plugin stores WooCommerce API keys, this flaw allows anyone to download credentials that act as a master key to the store.

How do attackers trigger this vulnerability?

An attacker triggers this by simply sending a web request to the specific, unprotected API endpoint provided by the plugin. No special preconditions, user accounts, or previous interactions are required. The bug is not triggered by standard site browsing; it requires a targeted request to the plugin's configuration path.

Is my site at risk according to Halo Surface Signal?

Yes, if your site uses this plugin, it is highly relevant. Halo Surface Signal identifies this as an external risk because the affected REST API endpoint is public by default on WordPress sites. If your store is reachable over the internet, an attacker can access this data remotely without needing internal network access.

How should I respond to this threat?

Start by auditing your WordPress environment to confirm if this specific plugin is installed and active. Determine if the plugin is necessary for your store's current operations. If it is in use, verify if the REST API endpoint is exposed to the internet and coordinate with your team to plan for updates or immediate removal to prevent credential theft.

References