Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit registration using victim's email
-
DeliveryTrigger email verification PIN step
-
ExploitBrute-force short numeric PIN unthrottled
-
ExecutionActivate account without mailbox control
-
ImpactGain authenticated WordPress session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK
2 techniques across 2 tactics: Defense Evasion, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the plugin's front-end user registration with email-verification be enabled, and depends on the verification code being a short numeric PIN with no limit on verification attempts (the missing rate-limit is the core flaw per CWE-287). The attacker must know or supply the target email address at registration time. The main limiting factor is that the attack only yields whatever privilege the plugin assigns to self-registered front-end accounts - typically low-privilege - rather than administrative access, and the site must actually offer public self-registration through Contest Gallery for the attack surface to exist. No authentication or user interaction is required (PR:N/UI:N). |
| Impact | This is a genuine but moderate-severity authentication weakness, not a critical priority. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms remote, unauthenticated, low-complexity exploitation with no user interaction, and the limited impact (C:N/I:L/A:N, base 5.3 Medium) is consistent with the outcome described: an attacker gains an authenticated account bound to an email they do not own, but does not directly compromise confidentiality or availability. No EPSS score, SSVC decision, KEV listing, or POC indicator was provided in the input, so exploitation-probability and automatability signals cannot be weighed - absence of these is not evidence of low risk, only of missing telemetry. The signals that ARE present are internally consistent (brute-forcing a short numeric PIN with no attempt limiting is inherently low-complexity and network-reachable), so there is no conflict between the CVSS vector and the description. Real-world priority is driven mainly by how the resulting account is used downstream: if the plugin's registration grants only subscriber-level access the impact is low, but if front-end accounts map to higher privileges or trusted identity, the integrity impact could be more serious than the base score suggests - verify the privilege level granted to registered accounts in the specific deployment. |
| Exploit ScenarioDerived | An unauthenticated attacker initiates front-end registration on a site running Contest Gallery, supplying a victim's email address, then repeatedly submits guesses against the short numeric email-verification PIN because the plugin enforces no attempt limit. Once a correct PIN is found, the account is activated and the attacker obtains an authenticated session tied to the victim's email without ever controlling that mailbox. No public exploit was identified in the provided data, but the technique requires only scripted HTTP requests. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Unrestricted brute-forcing of the email-verification PIN in the Contest Gallery WordPress plugin (all versions before 33.0.1) lets unauthenticated attackers guess a short numeric code and complete front-end registration for an email address they do not own, resulting in an authenticated WordPress session that the plugin treats as verified. Exploitation requires that the plugin's public front-end registration with email verification be enabled, and the practical ceiling is the privilege level the plugin assigns to self-registered accounts - typically low-privilege - rather than administrative access, which keeps this a genuine but moderate-severity authentication weakness rather than a critical one. No public exploit code was identified at time of analysis and the flaw is not confirmed actively exploited (no CISA KEV listing); the vendor has released a fix in version 33.0.1.
RemediationAI
Upgrade the Contest Gallery WordPress plugin to version 33.0.1 or later, which the vendor has released to address this issue; the WPScan advisory at https://wpscan.com/vulnerability/13853303-741e-4f87-8543-d5d825d20e8e/ is the authoritative reference. If the update cannot be applied immediately, the most effective compensating control is to disable the plugin's public front-end registration with email verification entirely, which removes the attack surface at the cost of losing self-service sign-up; alternatively, restrict registration to trusted email domains or to an approval workflow. Sites that must keep registration open can place rate limiting or bot mitigation in front of the verification endpoint at the WAF or reverse-proxy layer (for example, capping attempts per IP and per target email within a time window and blocking rapid sequential PIN submissions), accepting that this adds latency to legitimate users and can be evaded by distributed source IPs. Administrators should also audit existing accounts for suspicious or unverified-but-activated registrations bound to legitimate third-party email addresses, and consider enforcing confirmation on the account owner's side before granting any elevated role.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is rooted in CWE-287 (Improper Authentication) and, more specifically, the absence of attempt throttling on an authentication-adjacent verification step. Contest Gallery implements its own front-end sign-up flow inside WordPress rather than relying on core's registration, and that flow verifies a user's email by having them submit a short numeric PIN delivered to the address in question. Because the PIN space is small and the plugin imposes no per-account, per-IP, or per-session limit on verification attempts, the secret can be enumerated in a practical number of requests; the plugin then marks the account as activated and issues a session. This is distinct from a WordPress core or wp-login.php issue - the attack surface exists only where the plugin's public registration feature is in use, and the resulting account carries whatever role the plugin provisions for self-registered front-end users. Note that the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) reflects unauthenticated network exploitation with no user interaction and limited integrity impact, matching an account-integrity bypass rather than a confidentiality or availability breach.
Know when WordPress gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Remote unauthenticated brute-force of an unthrottled short PIN gives AV:N/AC:L/PR:N/UI:N; impact is account-integrity only, so I:L with C:N/A:N.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
The Contest Gallery WordPress plugin before 33.0.1 does not limit the number of attempts against its front-end registration email-verification step, which relies on a short numeric PIN, allowing unauthenticated attackers to brute-force the PIN and create and activate a WordPress account bound to an email address they do not own, gaining an authenticated session.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-96126
GHSA-4prj-22r4-mcwx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB