Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain contributor-level WordPress account
-
DeliveryAuthenticate to target WordPress site
-
ExploitSend order-retrieval requests with iterated order IDs
-
ExecutionBypass missing authorization check
-
ImpactHarvest customer PII from order records
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Exploitation requires an authenticated WordPress session with at minimum contributor-level role privileges - unauthenticated access is not sufficient. The vulnerable code path is within the Eventin plugin's order record retrieval functionality, which must be reachable (i.e., the plugin must be installed, active, and the site must have at least one recorded order). No special non-default configuration is required beyond having the Eventin plugin installed and operational. The key limiting factor is the contributor-level authentication prerequisite: an attacker must either possess a legitimate low-privilege account on the target WordPress installation or obtain one through registration (if open registration is enabled) or social engineering. Sites with open user registration accepting contributors are at higher risk. The scope is limited to Eventin order data only - this does not grant access to WordPress core user tables or other plugin data. |
| Impact | Despite a moderate CVSS base score of 4.3, several signals elevate real-world risk above the score alone. The EPSS score of 14% is high relative to typical WordPress plugin CVEs, suggesting active reconnaissance or exploitation attempts in the wild. A public proof-of-concept is documented by WPScan, confirming that exploitation capability is widely accessible. SSVC assessment confirms POC-level exploitation, non-automatable (contributor-level authentication is required, limiting mass exploitation), and partial technical impact. The confidentiality impact is the primary concern - customer PII exposure from order records can carry GDPR and PCI-DSS implications for affected site operators, which the raw CVSS score understates. A critical discrepancy exists in the provided CVSS vector: it reports C:N (no confidentiality impact) and I:L (low integrity impact), which is inconsistent with the description - the vulnerability explicitly enables reading other customers' personal information, a confidentiality breach, not an integrity violation. This suggests the NVD CVSS mapping may be erroneous; security teams should treat confidentiality as the primary impacted metric. The non-automatable SSVC rating is the key limiting factor: the contributor authentication prerequisite prevents unauthenticated mass exploitation. |
| Exploit ScenarioDerived | A threat actor registers a contributor account on a WordPress site running an unpatched version of Eventin - or an existing contributor-level employee acts maliciously. The attacker calls the order-retrieval endpoint repeatedly with sequentially iterated order IDs (e.g., order IDs 1 through 10,000), harvesting name, email, address, and purchase data for every customer who has placed an event ticket order. A public proof-of-concept from WPScan documents the exploitation method, making this accessible to low-skill attackers. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 13, 2026
Eventin WordPress plugin versions from 4.1.9 through 4.1.19 exposes customer order records - including personal information - to any contributor-level or higher WordPress user via an Insecure Direct Object Reference (IDOR) flaw. Authenticated users can enumerate order identifiers sequentially to read arbitrary customers' purchase data without authorization. A public proof-of-concept is available via WPScan, and an EPSS score of 14% places this notably above the median for WordPress plugin vulnerabilities, indicating active interest from threat actors even without a CISA KEV listing.
RemediationAI
The primary remediation is upgrading Eventin to version 4.1.20 or later, where vendor-released patch is available. Site administrators should apply this update immediately via the WordPress plugin dashboard or WP-CLI (wp plugin update eventin). As a compensating control prior to patching, restrict contributor-level role assignments on the WordPress site to only fully trusted users, since the flaw requires at minimum contributor access - reducing the contributor population directly limits the attack surface. If the event ticketing or order management features can be temporarily disabled via plugin settings without breaking critical site functionality, disabling order-view endpoints reduces exposure, though this may impact legitimate users. There are no known workarounds that eliminate the vulnerability without the patch; access-control plugins (e.g., Members, User Role Editor) cannot compensate for a missing server-side authorization check in the plugin's own code.
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 affected component is the Eventin event management WordPress plugin (CPE: cpe:2.3:a:unknown:eventin:*:*:*:*:*:*:*:*), an event ticketing and management solution. The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key), a classic IDOR pattern: the plugin's order-retrieval endpoint accepts a user-supplied order identifier but fails to verify that the requesting user is the owner of - or otherwise authorized to access - that order. Because order IDs are likely sequential integers, a contributor-level user can simply iterate over the ID space to harvest order records belonging to other customers. The CVSS vector PR:L confirms that a low-privilege WordPress account (contributor role) is sufficient to trigger the flaw, with no additional complexity barrier (AC:L). Note that CWE-639 is distinct from authentication bypass - the user IS authenticated, but the authorization gate on the object lookup is missing.
Know when Eventin 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:L/UI:N/S:U/C:N/I:L/A:N
Network-reachable IDOR exposing customer PII warrants C:L; no integrity or availability impact applies; PR:L reflects required contributor authentication.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Eventin WordPress plugin before 4.1.20 does not properly restrict access to individual order records, allowing users with contributor-level access and above to read other customers' order data including personal information by iterating order identifiers.
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.
Incorrect Privilege Assignment vulnerability in Themewinter Eventin allows Privilege Escalation.0.26. Rated critical sev
Unauthenticated account creation in the Eventin WordPress plugin (all versions before 4.1.20) allows any remote attacker
Eventin WordPress plugin versions before 4.1.20 exposes stored customer records - including names and email addresses -
Relative Path Traversal vulnerability in Themewinter Eventin allows Path Traversal.0.26. Rated high severity (CVSS 7.5),
Broken authorization in the Eventin WordPress plugin before 4.1.16 lets unauthenticated visitors create orders and suppl
Local file inclusion in the Eventin WordPress plugin (all versions before 4.1.20) allows authenticated users holding edi
Local file inclusion in Eventin WordPress plugin before 4.1.21 enables authenticated contributors and higher-privileged
Missing authorization in the Eventin WordPress plugin before 4.1.24 allows unauthenticated attackers to reuse the order-
Unauthenticated information disclosure in the Eventin WordPress plugin before 4.1.22 exposes private, draft, and pending
Unauthenticated payment bypass in the Eventin WordPress plugin before 4.1.19 lets any visitor fraudulently obtain valid
Unauthenticated visitors can mark unpaid Eventin orders of any value as paid by replaying a single genuine low-value pay
Missing authorization on Eventin's event-management REST routes allows low-privilege WordPress contributors to perform i
EUVD-2026-57075
GHSA-gf78-3gg4-868g
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB