CVE-2026-42689

Events Manager – Calendar, Bookings, Tickets, Appointments and more! <= 7.4.8 - Unauthenticated Race Condition

2026-10-12 00:00
Ananda Dhakal

Strategic Overview

Status
Unpatched
Affected Version
<= 7.4.8
CVSS
5.3Medium
Weakness type
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CVE
CVE-2026-42689
View all Events Manager – Calendar, Bookings, Tickets, Appointments and more! vulnerabilities

At a glance

CVE-2026-42689 is a medium-severity Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in the Events Manager WordPress plugin, affecting versions <= 7.4.8. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2026, reported by Ananda Dhakal.

Vulnerability Overview

The Events Manager – Calendar, Bookings, Tickets, Appointments and more! plugin for WordPress is vulnerable to a Race Condition in all versions up to, and including, 7.4.8. This makes it possible for unauthenticated attackers to perform an unauthorized action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C