CVE-2024-6033

Event Manager, Events Calendar, Tickets, Registrations – Eventin <= 4.0.4 - Missing Authorization to Authenticated (Contributor+) Event Data Import

2024-07-16 00:00
Peter Thaleikis

Strategic Overview

Status
Patched in 4.0.5
Affected Version
<= 4.0.4
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-6033
View all Eventin – Event Calendar, Tickets, Registration, Booking & WooCommerce vulnerabilities

At a glance

CVE-2024-6033 is a medium-severity Missing Authorization vulnerability in the Eventin WordPress plugin, affecting versions <= 4.0.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.0.5; sites on affected versions should update now. Disclosed July 2024, reported by Peter Thaleikis.

Vulnerability Overview

The Event Manager, Events Calendar, Tickets, Registrations – Eventin plugin for WordPress is vulnerable to unauthorized data importation due to a missing capability check on the 'import_file' function in all versions up to, and including, 4.0.4. This makes it possible for authenticated attackers, with Contributor-level access and above, to import events, speakers, schedules and attendee data.

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

Eventin <= 4.0.4 carries this weakness at import_file, and reaching it takes an account at Contributor 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 Eventin the fix is 4.0.5: builds <= 4.0.4 are affected, anything from 4.0.5 onward is not.

Remediation

Update to version 4.0.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: Eventin 4.0.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