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

CVE-2024-43138

HIGH · 8.8 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 4.2.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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in MagePeople Team Event Manager for WooCommerce allows PHP Local File Inclusion.This issue affects Event Manager for WooCommerce: from n/a through 4.2.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 · high confidence

A path traversal vulnerability in MagePeople Team Event Manager for WooCommerce (versions through 4.2.1) allows attackers to perform local file inclusion. The plugin fails to properly validate file path inputs, enabling attackers to escape restricted directories and include arbitrary PHP files, potentially leading to sensitive data disclosure or remote code execution.

MitigationApply vendor-supplied patch or update to version 4.2.2 or later. If no patch available, implement input validation whitelisting on all file path parameters and disable PHP execution in upload directories.

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.2.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. Identify the installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > Find 'Mage People Event Manager And Tickets Selling For Woocommerce' and check the version number displayed
    Affected if The version listed is below 4.2.2
  2. Locate the plugin files on the server
    Check the wp-content/plugins/ directory for the plugin folder name (typically contains 'mage' or 'event-manager'), then view the main plugin PHP file header for the Version constant
    Affected if The plugin version cannot be verified as 4.2.2 or higher
  3. Inspect web server access logs for path traversal patterns
    Search access logs (通常在 /var/log/apache2/access.log, /var/log/nginx/access.log, 或托管提供商的日志) for requests containing '../' or '..%2F' patterns targeting the plugin endpoints
    Affected if Logs show directory traversal attempts to plugin files (e.g., ?file=../../../../etc/passwd)
  4. Review plugin configuration files for unauthorized changes
    Examine configuration files within the plugin directory for any recently modified PHP files or added suspicious code that may indicate exploitation
    Affected if Configuration files contain unexpected includes or file reading logic using user-supplied input

You are affected if the MagePeople Event Manager plugin is installed at a version below 4.2.2, or if web server logs show directory traversal attempts targeting this plugin.

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.2.2 or later
Fixed in 4.2.2
Interim mitigation

Apply vendor-supplied patch or update to version 4.2.2 or later. If no patch available, implement input validation whitelisting on all file path parameters and disable PHP execution in upload directories.

Recommended fix Moderate confidence

4.2.2

  1. 1. Create a complete backup of your WordPress site including the database and all files.
  2. 2. Log in to your WordPress admin dashboard.
  3. 3. Navigate to Plugins > Installed Plugins.
  4. 4. Find 'Event Manager And Tickets Selling For WooCommerce' in the plugin list.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 4.2.2 or later.
  6. 6. Alternatively, download version 4.2.2 from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin version shows 4.2.2 or higher in the plugins list.
  8. 8. Test the event management functionality to ensure the plugin works correctly after the update.

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
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43138 — 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-43138 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