CVE-2026-123698VulnerabilityPublished 11 Nov 2026

The Security For WooCommerce WordPress plugin through 1.0.16 does not restrict access to one of its REST API routes

Source GCVE Database

Compare

Authoritative record:CVE-2026-123698· High

Not known to be exploited.

Data as of 11 Nov 2026, 07:32 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-9w8w-cqc3-2qh3

What to do

Affected software

Product	Affected	Fixed in
Security For WooCommerce	Affected <=1.0.16	Fixed in–

AI-suggested

Until a fix is available, restrict access to the affected REST API route by implementing access controls or disabling the route if possible.

Description

The Security For WooCommerce WordPress plugin up to version 1.0.16 has a vulnerability where one of its REST API routes is accessible without authentication. This flaw allows unauthenticated users to retrieve the plugin's full settings, including secret keys and the hidden login URL.

Impact

An attacker can obtain sensitive configuration details including secret keys and the hidden login URL without authentication. This exposure could facilitate further attacks against the WordPress site by bypassing security controls or gaining unauthorized access.

Summary

The Security For WooCommerce WordPress plugin through version 1.0.16 does not properly restrict access to a REST API route. As a result, unauthenticated users can access sensitive configuration data such as secret keys and the hidden login URL, potentially compromising the security of the plugin and the WordPress site.

References

Community reviews

Loading reviews…