PatchSiren cyber security CVE debrief
CVE-2026-110955 Wurdey CVE debrief
The Wurdey WordPress plugin through 1.0.0 does not verify a request signature before logging a user in, allowing unauthenticated attackers to authenticate as an administrator knowing only the administrator's username. This vulnerability allows attackers to bypass authentication mechanisms, potentially leading to unauthorized access and control of WordPress installations. Defenders should assess exposure and prioritize patching or mitigation to prevent exploitation. The CVE record and NVD entry provide details on the vulnerability, but additional verification is needed to confirm affected versions and remediation.
- Vendor
- Wurdey
- Product
- Wurdey WordPress plugin
- CVSS
- CRITICAL 9.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-11-06
- Original CVE updated
- 2026-11-06
- Advisory published
- 2026-11-06
- Advisory updated
- 2026-11-06
Who should care
WordPress administrators and defenders responsible for securing WordPress installations should assess exposure and prioritize patching or mitigation.
Why it matters
CVE-2026-110955 allows unauthenticated attackers to authenticate as administrators in WordPress installations using the Wurdey plugin. Defenders should prioritize verifying exposure, applying patches, and monitoring for suspicious activity.
- Unauthenticated attackers can gain administrative access
- Defenders must verify plugin presence and version
- Patching or mitigation is required to prevent exploitation
- Additional monitoring may be necessary to detect suspicious activity
Technical summary
The Wurdey WordPress plugin through 1.0.0 does not verify a request signature before logging a user in, allowing unauthenticated attackers to authenticate as an administrator knowing only the administrator's username. This vulnerability is caused by a lack of request signature verification, enabling attackers to authenticate as administrators without proper credentials. To mitigate this vulnerability, defenders should verify the presence of the Wurdey plugin in their WordPress installations, check if the plugin version is 1.0.0 or earlier, and apply patches or as
Defensive priority
Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations and apply patches or mitigations as available.
Recommended defensive actions
- Verify the presence of the Wurdey WordPress plugin in your environment
- Check if the plugin version is 1.0.0 or earlier
- Apply patches or updates as available
- Monitor for suspicious login attempts
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, but additional verification is needed to confirm affected versions and remediation.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-110955 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-110955
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-110955 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-110955
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://wpscan.com/vulnerability/3a1a4bb4-01ce-4b4b-8493-4b1a857d2c03/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.