Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site running Eventin plugin
-
DeliverySend unauthenticated GET request to vulnerable REST API namespace
-
ExploitEnumerate non-public post IDs
-
ExecutionRetrieve full content of private/draft/password-protected posts
-
ImpactExfiltrate post passwords and sensitive content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions are required for exploitation: the Eventin plugin (any version before 4.1.22) simply needs to be installed and active on a WordPress site accessible over the network. The CVSS vector AV:N/AC:L/PR:N/UI:N confirms remote, unauthenticated exploitation against default plugin configurations with no user interaction. The limiting factor is that impact is restricted to confidentiality only - no content modification or site takeover is possible through this flaw alone. Exploitation is further limited to sites that actually have private, draft, pending, or password-protected posts; sites using Eventin purely for public event listings with no restricted content have reduced data exposure risk, though the endpoint remains accessible. |
| Impact | The CVSS 5.3 (Medium) score reflects a purely confidentiality-limited, unauthenticated network-accessible flaw with no integrity or availability impact - consistent with the actual behavior described. The EPSS score of 0.18% (7th percentile) indicates statistically low exploitation probability, and SSVC confirms exploitation status as 'none' at time of analysis, meaning no active exploitation has been observed. However, the SSVC also rates the attack as 'Automatable: yes,' meaning mass scanning and bulk exfiltration of private post content from all vulnerable Eventin installations is trivially achievable with a script - even a small hosting provider or municipal WordPress deployment should not treat the low EPSS as a reason to delay patching. A publicly available exploit exists per the WPScan reference, which elevates the realistic near-term risk above what the EPSS percentile alone would suggest. The combination of no authentication required, full network accessibility, and a public PoC means the window between patch release and active exploitation may be short. The moderate CVSS score is accurate but should not be taken as license to deprioritize patching - the automatable, unauthenticated nature of the flaw makes it a candidate for opportunistic mass exploitation. |
| Exploit ScenarioDerived | An unauthenticated attacker sends HTTP GET requests to the vulnerable Eventin REST API namespace endpoint - no credentials, tokens, or prior reconnaissance of user accounts required. The attacker enumerates and downloads the full content of all draft, pending, private, and password-protected posts, including their plaintext access passwords. A publicly available proof-of-concept makes this trivially scriptable for bulk scanning across many WordPress installations. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 26, 2026
Unauthenticated information disclosure in the Eventin WordPress plugin before 4.1.22 exposes private, draft, and pending posts - including the plaintext passwords and full content of password-protected posts - to any unauthenticated HTTP client via an unprotected REST API namespace. The flaw arises from missing authorization checks on post status and ownership within that namespace, meaning no credentials or privileges are required to enumerate and read content the site owner intended to restrict. A publicly available proof-of-concept exploit exists, and the attack is fully automatable per the SSVC framework, though CISA has not listed this in KEV and the EPSS score is low (0.18%), suggesting exploitation has not yet been widespread.
RemediationAI
Update the Eventin WordPress plugin to version 4.1.22 or later, which is confirmed as the patched release per the vendor advisory referenced in the WPScan report at https://wpscan.com/vulnerability/1b2d4b55-1b7e-4150-8f90-492f7a3d5400/. Patching is the only complete fix because the vulnerability is in the plugin's REST API namespace registration. If immediate update is not possible, a compensating control is to disable the WordPress REST API for unauthenticated users using a security plugin (e.g., Disable REST API or equivalent), though this may break legitimate frontend functionality that depends on the API. Alternatively, a WAF rule blocking unauthenticated requests to the Eventin REST API namespace path can reduce exposure, but the exact namespace path should be confirmed from the WPScan advisory before relying on this control. Site administrators should also audit any password-protected posts whose passwords may have been exposed, as those passwords could have been harvested prior to patching.
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
Eventin is a WordPress event management plugin. WordPress exposes functionality through REST API namespaces; plugins register their own endpoints and are responsible for applying capability checks (e.g., via permission_callback) to enforce authorization. CWE-862 (Missing Authorization) identifies the root cause: one of Eventin's REST API namespaces omits these checks, failing to validate whether the requesting user has rights to view posts that are not publicly published. This means WordPress's own post-visibility controls (draft, pending, private, password-protected statuses) are bypassed entirely at the API layer. The CPE string (cpe:2.3:a:unknown:eventin:*:*:*:*:*:*:*:*) covers all versions prior to 4.1.22 as affected. The disclosure of password-protected post passwords is a particularly sensitive sub-impact, as those passwords may be reused elsewhere.
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:N/UI:N/S:U/C:L/I:N/A:N
Unauthenticated network access with no complexity; confidentiality-only impact limited to non-public post content, no integrity or availability effect.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Eventin WordPress plugin before 4.1.22 does not restrict access to non-published content by status or ownership in one of its REST API namespaces, allowing unauthenticated users to retrieve draft, pending and private posts belonging to other users, along with the passwords and contents of password-protected ones.
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
Eventin WordPress plugin versions from 4.1.9 through 4.1.19 exposes customer order records - including personal informat
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 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-66265
GHSA-fpv5-766g-3798
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB