dbcve.org
EventerWordPress extension · Imithemes

CVE-2024-10799

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-17
Fix available
A fix is available. Upgrade to 3.9.8 or later.
See remediation →
71/100
Remediation priority · Elevated
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
The Eventer plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 3.9.7 via the eventer_woo_download_tickets() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

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

The Eventer WordPress plugin contains a directory traversal vulnerability in the eventer_woo_download_tickets() function, allowing authenticated users with Subscriber-level access or higher to read arbitrary files on the server by manipulating file path parameters.

MitigationUpdate the Eventer plugin to version 3.9.8 or later. If immediate update is not possible, consider restricting subscriber-level user capabilities or implementing web server-level access controls to limit file system access.

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
EventerWordPress extension
Affected:< 3.9.8

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
None
Availability
None

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

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 Eventer plugin is installed
    Navigate to WordPress admin dashboard > Plugins and locate 'Eventer' by Imithemes, or check the plugin files in wp-content/plugins/eventer/ for the main PHP file and its version header
    Affected if Eventer plugin is present in the WordPress installation
  2. Determine installed Eventer version
    In WordPress admin, go to Plugins > Installed Plugins > Eventer and note the version number displayed, or open the main plugin PHP file (e.g., eventer.php) and read the Version: header in the plugin comments
    Affected if Version is lower than 3.9.8 (e.g., 3.9.7, 3.9.6, etc.)
  3. Check if WooCommerce integration is enabled
    In WordPress admin, go to Eventer settings > WooCommerce tab (or Event Settings > WooCommerce integration) and verify whether the 'Enable WooCommerce Tickets' or similar option is turned on
    Affected if WooCommerce ticket functionality is active and accessible
  4. Confirm subscriber-level user accounts exist
    In WordPress admin, go to Users and review the list. Any user with the 'Subscriber' role (role column shows 'Subscriber') can trigger the vulnerable function if WooCommerce integration is enabled
    Affected if At least one user with Subscriber role exists and can access the site

User is affected if Eventer plugin version is below 3.9.8 AND WooCommerce tickets integration is enabled AND subscriber-level users have site access.

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 3.9.8 or later
Fixed in 3.9.8
Interim mitigation

Update the Eventer plugin to version 3.9.8 or later. If immediate update is not possible, consider restricting subscriber-level user capabilities or implementing web server-level access controls to limit file system access.

Recommended fix High confidence

3.9.8

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Eventer plugin in the list
  4. Check if the current version is below 3.9.8
  5. If vulnerable, click 'Update Now' to update to the latest version (3.9.8 or later)
  6. Alternatively, download the updated plugin from the official WordPress plugin repository or codecanyon.net
  7. Verify the update was successful by checking the plugin version after updating

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

Fix this in Eventer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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