# CVE-2026-100109: Security For WooCommerce 1.0.10 - 1.0.16 - Unauthenticated Privilege Escalation via usfw_create_temporary_user

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

The Security For WooCommerce WordPress plugin from 1.0.10 to 1.0.16 does not perform capability checks when creating users through an action available to unauthenticated visitors, and lets the caller choose the new account's role, allowing unauthenticated attackers to create administrator accounts and take over the site.

## Remediation

No remediation reported in collected sources

## Affected products and versions

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

## Severity and prioritization

- CVSS 3.0: 9.8 (critical); CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; source: CNA: WPScan

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-862

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/b4d26eb3-ab32-456e-9f69-9ab300fdf44c/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/b4d26eb3-ab32-456e-9f69-9ab300fdf44c/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

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

Revision: b712054b57ae7e93ad8f25fd8156bee53af86fd42f8bc978722712f26378726c

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

## 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.