Event MonsterWordPress extension · Awplife
CVE-2024-11396
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 Event Monster – Event Management, Tickets Booking, Upcoming Event plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.4.3 via the Visitors List Export file. During the export, a CSV file is created in the wp-content folder with a hardcoded filename that is publicly accessible. This makes it possible for unauthenticated attackers to extract data about event visitors, that includes first and last names, email, and phone number.
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 Event Monster WordPress plugin versions up to 1.4.3 creates a CSV file containing event visitor PII (first name, last name, email, phone) in the wp-content directory during the Visitors List Export function. This file uses a hardcoded, predictable filename that is publicly accessible without authentication, allowing any unauthenticated attacker to download sensitive visitor data.
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 MonsterWordPress extension
< 1.4.4CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Event Monster plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Event Monster and verify the version number. Alternatively, check the plugin header in /wp-content/plugins/event-monster/event-monster.php for the Version field.Affected if Version is 1.4.3 or lower (less than 1.4.4)
-
Locate the exposed CSV file in wp-contentList all CSV files in the /wp-content/ directory. Look for any CSV file with a name that may contain 'visitor', 'export', 'list', or similar terms indicating event visitor data.Affected if A CSV file containing visitor PII exists in wp-content with a predictable/hardcoded name
-
Verify public accessibility of the CSV fileAttempt to access the suspected CSV file via a web browser or curl using the wp-content path, for example: https://yourdomain.com/wp-content/[suspected-filename].csv. No authentication should be required for a successful download.Affected if The CSV file is publicly accessible without authentication (returns HTTP 200)
-
Check server access logs for export function usageSearch access logs (usually in /var/log/apache2/ or /var/log/nginx/) for requests to the Visitors List Export function. Look for POST or GET requests to paths containing 'visitor-export', 'export-visitors', or the plugin's export endpoint.Affected if Logs show the export function was invoked, confirming the vulnerable feature was used
You are affected if the Event Monster plugin version is below 1.4.4 AND the plugin's Visitors List Export feature was used, resulting in a publicly accessible CSV file in wp-content containing visitor PII.
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 · scoped1.4.4
Update to version 1.4.4 or later immediately. Additionally, audit and delete any exposed CSV files in wp-content that may have been created by this plugin, as the vulnerable file may have already been exfiltrated.
Event Monster version 1.4.4
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in WordPress admin
- Find the Event Monster plugin and click Update Now, or manually upload version 1.4.4
- Verify the plugin is now running version 1.4.4
- Check that the vulnerable CSV file in wp-content has been removed or renamed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Event Monster
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11396 — 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-11396 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