# CVE-2026-123699: Security For WooCommerce <= 1.0.16 - Unauthenticated Forced Plugin, Theme and Core Updates

Status: published. Published: 2026-11-11. Updated: 2026-11-11.

The Security For WooCommerce WordPress plugin through 1.0.16 does not check that the requester is authorised before running bulk Security For WooCommerce WordPress plugin through 1.0.16,  and WordPress core updates, allowing unauthenticated users to force every pending update to be installed on the site.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / Security For WooCommerce: ≥ 0; ≤ 1.0.16 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-862

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/344ca520-dc28-4d52-a400-559d23359d23/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/344ca520-dc28-4d52-a400-559d23359d23/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2026-123699; retrieved 2026-11-11; source updated 2026-11-11

Revision: 1789d4fcef6b012f6a8def466885e4d3cdb3de9bd10dd9cc159f389b6575b040

Canonical: https://y2.dev/cve/CVE-2026-123699

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.