CVE-2026-110955VulnerabilityPublished 6 Nov 2026

The Wurdey WordPress plugin through 1.0.0 does not verify a request signature before logging a user in, allowing

Source GCVE Database

Compare

Authoritative record:CVE-2026-110955· High

Not known to be exploited.

Data as of 6 Nov 2026, 07:33 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 6 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 5 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-v6ww-57fq-qg7p

What to do

Affected software

Product	Affected	Fixed in
Wurdey	Affected <=1.0.0	Fixed in–

AI-suggested

Until a fix is available, restrict access to the plugin or disable it if possible to prevent exploitation.

Description

The Wurdey WordPress plugin versions up to 1.0.0 contains a vulnerability where it does not verify request signatures before logging users in. This flaw allows unauthenticated attackers to log in as an administrator if they know the administrator's username.

Impact

An attacker can authenticate as an administrator without valid credentials, solely by knowing the administrator's username. This grants full administrative privileges, potentially allowing complete control over the affected WordPress site.

Summary

The Wurdey WordPress plugin through version 1.0.0 fails to verify a request signature prior to authenticating a user. This lack of verification enables unauthenticated attackers to bypass normal authentication controls and gain administrator access by simply knowing an administrator's username.

References

Community reviews

Loading reviews…