EUVD-2026-85039
GHSA-4882-xrgv-cg68
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege (contributor) account
-
ExploitSend crafted REST API create/update request
-
ExecutionServer skips publish capability check
-
ImpactContent published bypassing editorial review
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
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 | Exploitation requires an authenticated WordPress account with a role that can create but not publish content (e.g., Contributor) on a site running The Events Calendar versions 6.15.0 up to but not including 6.17.5. The attacker must reach the plugin's REST API endpoints used to create or update content. Limiting factors: authentication is required (some level of account access must exist), and the impact is confined to publishing content without editorial review (integrity only) - there is no confidentiality or availability impact and no code execution. No user interaction by a victim is needed. |
| Impact | This is a low-severity broken-access-control flaw (CWE-863) with limited real-world urgency. The provided CVSS vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N = 2.7) reflects a network-reachable, low-complexity issue with integrity-only impact (I:L) and no confidentiality or availability effect. There is a notable internal conflict: WPScan scored PR:H, but the description states the actor is a low-privilege 'contributor' role, which normally maps to PR:L - this discrepancy inflates the barrier to entry in the score and should be verified (the real prerequisite is any authenticated account that can submit-but-not-publish, i.e., PR:L). No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no signal of active or automated exploitation. The impact is editorial-workflow bypass (a contributor publishing without review), not data theft or code execution, so this is a genuine-but-minor governance/integrity issue rather than a security emergency - appropriate to patch in normal maintenance cycles. |
| Exploit ScenarioDerived | An attacker who has obtained (or been granted) a low-privilege WordPress account such as Contributor on a site running The Events Calendar sends a crafted request to the plugin's REST API to create or update content, which fails to enforce the publish capability and pushes the content live. This lets untrusted contributors bypass editorial moderation to publish spam, misinformation, or unauthorized posts directly. No public exploit code was identified at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Contributors on WordPress sites running The Events Calendar versions 6.15.0 through 6.17.4 can bypass editorial review and publish events or other content directly through the plugin's REST API. The flaw, a missing capability check (CWE-863), lets authenticated low-privilege users perform actions they are not authorized to do, though impact is limited to integrity without confidentiality or availability loss. No public exploit code has been identified, and the issue is not listed in CISA KEV; severity is low per the assessed vector.
RemediationAI
Upgrade The Events Calendar plugin to version 6.17.5 or later, which contains the vendor patch that adds the missing capability check. Since the plugin is distributed through WordPress.org, updates can be applied via the WordPress admin dashboard or WP-CLI. If immediate upgrade is not possible, mitigate by temporarily removing Contributor-level accounts or restricting their ability to access the plugin's REST API endpoints (e.g., by using a security plugin to enforce role-based access controls or by disabling the plugin's REST routes until patched). Note that these workarounds may disrupt legitimate event submission workflows and do not fully eliminate the risk. Monitor published content for unauthorized posts. Refer to the vendor advisory at https://wpscan.com/vulnerability/f9228a51-1293-4a96-95da-0e57b7eb5f6b/ for details. Patch status: Vendor-released patch: 6.17.5.
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 Events Calendar is a WordPress plugin that extends the WordPress REST API to allow creation and updating of events and related content. The vulnerability arises because the plugin's REST API endpoints do not properly check the user's capability to publish content (e.g., the publish_posts capability) before performing create or update operations. This falls under CWE-863 (Incorrect Authorization), allowing a user with a Contributor role-who can create but not publish-to publish content directly. The affected versions are 6.15.0 through 6.17.4; the fix in 6.17.5 adds the missing capability check. No CPE string was provided, but the affected component is the WordPress plugin identified by its slug 'the-events-calendar'.
Know when PHP 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:H/UI:N/S:U/C:N/I:L/A:N
Contributor is a low-privilege authenticated role, so PR:L (not PR:H); network REST API, low complexity; integrity-only impact from unauthorized publishing so I:L, C:N/A:N.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
The Events Calendar WordPress plugin before 6.17.5 does not check the capability required to publish content before creating or updating it through its REST API, allowing users with a role that cannot normally publish, such as contributor, to publish content directly and bypass editorial review.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
Exploit-DB