# CVE-2026-123697: Security For WooCommerce <= 1.0.16 - Unauthenticated Two-Factor Code and Secret Disclosure

> Unauthenticated users can obtain two-factor codes and secrets for any account, bypassing 2FA on sites using the Security For WooCommerce plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-cg7c-763h-xv22

## What is CVE-2026-123697?

CVE-2026-123697 is a high-severity missing authorization vulnerability in Unknown Security For WooCommerce, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Security For WooCommerce WordPress plugin through 1.0.16 does not restrict who can request a user's current two-factor code or two-factor secret, allowing unauthenticated users to obtain them for any account and bypass the second factor on sites where its one-time password library is available.

Weakness: CWE-862 (Missing Authorization)

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

Only installations with a non-default setting turned on are exposed.


## How do I fix CVE-2026-123697?

No fix has been published for CVE-2026-123697 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123697 being exploited?

There is no known exploitation of CVE-2026-123697 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123697 and fix it if it is affected.

What it is: CVE-2026-123697 is a high-severity missing authorization vulnerability in Unknown Security For WooCommerce, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-123697 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

Affected product: Unknown Security For WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123697/ (Markdown: https://insights.sbomify.com/CVE-2026-123697/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123697
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123697
- OSV: https://osv.dev/vulnerability/CVE-2026-123697

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123697/
Summaries are generated and may contain mistakes; the official description above is the record.