CVE-2023-4251

EventPrime < 3.2.0 - Cross-Site Request Forgery

2023-10-09 00:00
Alex Sanford

Strategic Overview

Status
Patched in 3.2.0
Affected Version
< 3.2.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-4251
View all EventPrime – Events Calendar, Bookings, Tickets & AI vulnerabilities

At a glance

CVE-2023-4251 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the EventPrime WordPress plugin, affecting versions < 3.2.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.2.0; sites on affected versions should update now. Disclosed October 2023, reported by Alex Sanford.

Vulnerability Overview

The EventPrime plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to 3.2.0. This is due to missing or incorrect nonce validation one of its functions. This makes it possible for unauthenticated attackers to create event bookings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE-2023-5519 appears to be a duplicate assignment for this issue.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in EventPrime < 3.2.0 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For EventPrime the fix is 3.2.0: builds < 3.2.0 are affected, anything from 3.2.0 onward is not.

Remediation

Update to version 3.2.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to EventPrime: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: EventPrime 3.2.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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