CVE-2026-1655

EventPrime <= 4.2.8.4 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Event Modification via 'event_id' Parameter

2026-02-17 19:22
Supoj Polsawas (sp0x5ec)

Strategic Overview

Status
Patched in 4.2.8.5
Affected Version
<= 4.2.8.4
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-1655
View all EventPrime – Events Calendar, Bookings, Tickets & AI vulnerabilities

At a glance

CVE-2026-1655 is a medium-severity Missing Authorization vulnerability in the EventPrime WordPress plugin, affecting versions <= 4.2.8.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.2.8.5; sites on affected versions should update now. Disclosed February 2026, reported by Supoj Polsawas (sp0x5ec).

Vulnerability Overview

The EventPrime plugin for WordPress is vulnerable to unauthorized post modification due to missing authorization checks in all versions up to, and including, 4.2.8.4. This is due to the save_frontend_event_submission function accepting a user-controlled event_id parameter and updating the corresponding event post without enforcing ownership or capability checks. This makes it possible for authenticated (Customer+) attackers to modify posts created by administrators by manipulating the event_id parameter granted they can obtain a valid nonce.

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 interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in EventPrime <= 4.2.8.4 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For EventPrime the fix is 4.2.8.5: builds <= 4.2.8.4 are affected, anything from 4.2.8.5 onward is not.

Remediation

Update to version 4.2.8.5, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: EventPrime 4.2.8.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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