dbcve.org
Event Manager And Tickets Selling For WoocommerceWordPress extension · Mage People

CVE-2024-24796

HIGH · 8.8 CVSS v3.1 Published 2024-02-12
Fix available
A fix is available. Upgrade to 4.1.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Deserialization of Untrusted Data vulnerability in MagePeople Team Event Manager and Tickets Selling Plugin for WooCommerce – WpEvently – WordPress Plugin.This issue affects Event Manager and Tickets Selling Plugin for WooCommerce – WpEvently – WordPress Plugin: from n/a through 4.1.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a deserialization of untrusted data vulnerability in the WpEvently WordPress plugin for WooCommerce. Attackers can potentially inject malicious serialized data that gets deserialized by the application, which may lead to remote code execution depending on the application's deserialization logic and available PHP classes.

MitigationUpdate the WpEvently plugin to the latest version after 4.1.1. If no patch is available, consider disabling the plugin until a fix is released, or implement web application firewall rules to detect and block malicious serialized data patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Event Manager And Tickets Selling For WoocommerceWordPress extension
Affected:< 4.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Mage People Event Manager And Tickets Selling For Woocommerce' or 'WpEvently' in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Check installed version
    In WordPress admin > Plugins, find the plugin and view the version number displayed under the plugin name, or inspect the plugin header in the main plugin file (usually in wp-content/plugins/mage-people-event-manager/ or similar path)
    Affected if The installed version is lower than 4.1.2 (e.g., 4.1.1, 4.1.0, or earlier)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the plugin status shows as 'Active'
    Affected if The plugin is currently activated on the WordPress site
  4. Check for deserialization exposure
    Review the plugin's PHP files for use of unserialize() function on data that could come from user input (GET/POST parameters, cookies, API requests). Common patterns include: unserialize($_POST['data']), unserialize($_REQUEST['...]), or similar. Use grep to search: grep -r "unserialize" /path/to/wp-content/plugins/mage-people-event-manager/
    Affected if The plugin code contains unserialize() calls processing external input without prior sanitization

The site is affected if the Mage People Event Manager And Tickets Selling For Woocommerce plugin is installed with a version below 4.1.2 and the plugin is active, as the deserialization vulnerability can be triggered by attackers injecting malicious serialized data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.1.2 or later
Fixed in 4.1.2
Interim mitigation

Update the WpEvently plugin to the latest version after 4.1.1. If no patch is available, consider disabling the plugin until a fix is released, or implement web application firewall rules to detect and block malicious serialized data patterns.

Recommended fix High confidence

4.1.2

  1. 1. Back up your WordPress site (database and files) before making any changes
  2. 2. Log in to the WordPress admin dashboard
  3. 3. Navigate to Plugins > Installed Plugins
  4. 4. Find 'Event Manager and Tickets Selling Plugin for WooCommerce – WpEvently'
  5. 5. If an update is available, click 'Update Now' to upgrade to version 4.1.2
  6. 6. Alternatively, download version 4.1.2 from the official WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the plugin version shows 4.1.2 in the plugins list
  8. 8. Test critical ticketing and event management functionality to ensure the update does not break existing features
Caveat Review the plugin changelog before updating to check for any breaking changes or feature modifications in version 4.1.2

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Event Manager And Tickets Selling For Woocommerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24796 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-24796 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data