CVE-2026-123703VulnerabilityPublished 11 Nov 2026

The Security For WooCommerce WordPress plugin through 1.0.16 does not check that the requester is authorised before

Source GCVE Database

Compare

Authoritative record:CVE-2026-123703· Medium

Not known to be exploited.

Data as of 11 Nov 2026, 07:20 UTC

Severity

Medium

Rated Medium 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-wq3v-4v6v-9h3h

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, consider restricting access to the logout functionality or monitoring for suspicious logout requests.

Description

The Security For WooCommerce WordPress plugin versions through 1.0.16 contain a vulnerability that allows unauthenticated users to forcibly log out any user, including administrators, by exploiting a lack of authorization checks when ending user sessions. Attackers can repeatedly send logout requests to keep targeted users logged out.

Impact

An attacker can disrupt user sessions by logging out users without authentication, potentially causing denial of service to administrators and other users by preventing them from remaining logged in.

Summary

The Security For WooCommerce WordPress plugin up to version 1.0.16 does not verify whether the requester is authorized before terminating a user's login session. This flaw enables unauthenticated visitors to log out any user, including administrators, and maintain their logged-out state by repeatedly issuing logout requests.

References

Community reviews

Loading reviews…