EventerWordPress extension · Imithemes
CVE-2024-11134
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 · uneditedThe Eventer plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'eventer_export_bookings_csv' function in all versions up to, and including, 3.9.9. This makes it possible for authenticated attackers with subscriber-level permissions or above, to download bookings, which contains customers' personal data.
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 confidenceThe Eventer WordPress plugin has a missing capability check on the 'eventer_export_bookings_csv' function in versions up to 3.9.9. This allows any authenticated user with subscriber-level permissions to export booking data containing customer PII without authorization.
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
< 3.9.9.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Eventer plugin versionIn WordPress admin, go to Plugins > Installed Plugins > find Eventer by Imithemes and note the version number. Alternatively, inspect the plugin header in wp-content/plugins/eventer/includes/eventer.php or the main plugin file.Affected if The version listed is below 3.9.9.1 (any version up to and including 3.9.9)
-
Verify bookings feature is enabledNavigate to Eventer plugin settings in WordPress admin and check if the bookings functionality is active. Look for booking management menus or settings related to event reservations.Affected if Bookings feature is enabled and functional in the plugin
-
Identify subscriber-level user accountsIn WordPress admin, go to Users > All Users and review the list. Note any users assigned the Subscriber role. Also check for any custom roles that have equivalent or lower permission levels than Subscriber.Affected if There exists at least one user account with Subscriber role or a custom role with similar low-level permissions
-
Confirm export functionality is accessibleAttempt to access the CSV export endpoint directly, or check if the eventer_export_bookings_csv function exists in the plugin files without capability checks in the code. Look for the function in the plugin includes folder.Affected if The eventer_export_bookings_csv function exists and can be called by any authenticated user without elevated permissions
A user is affected if they run Eventer version below 3.9.9.1, have the bookings feature enabled, and have at least one subscriber-level user account, allowing unauthorized PII export.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.9.9.1
Update to version 3.9.10 or later which includes proper capability checks to verify user permissions before allowing CSV export of bookings.
Eventer version 3.9.9.1
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the Eventer plugin in the list
- Check if the current version is below 3.9.9.1
- If update available, click 'Update Now' to upgrade to version 3.9.9.1
- Alternatively, navigate to Dashboard > Updates and select Eventer to update
- Verify the update completed successfully by checking the plugin version
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
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11134 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-11134 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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