CVE-2024-11396
Awplife Event Monster ≤ 1.4.4
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-11396 is a medium-severity Exposure of Private Personal Information to an Unauthorized Actor (CWE-359) vulnerability in Awplife Event Monster. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked in the top 19% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-21 (Information Sharing) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The Event Monster – Event Management, Tickets Booking, Upcoming Event plugin for WordPress is vulnerable to information exposure in all versions through 1.4.3. The flaw resides in the Visitors List Export feature, which writes a CSV file containing attendee details to a hardcoded, publicly reachable path under wp-content during export processing.
Unauthenticated remote attackers can simply request the predictable CSV filename to obtain first and last names, email addresses, and phone numbers of event visitors. The issue requires no credentials, user interaction, or special network conditions, corresponding to the observed CVSS 5.3 rating.
References from Wordfence and the plugin source repository confirm the exposure path but do not detail specific patch contents or mitigation steps beyond upgrading past version 1.4.3. The EPSS score currently sits at 0.6027 with a peak of 0.6048; no material rise from a low baseline is indicated in the supplied data.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-34166
Vulnerability Data
The 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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
V10.3.5V10.7.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces authorizations so that PII is not reachable by unauthorized actors.
Requires explicit verification that a recipient's authorizations match the sensitivity of shared PII.
Limits granted rights to the minimum needed, reducing the set of actors who can reach private data.
Documents the legal or consent basis required before any processing of PII occurs.
Implements consent mechanisms that directly block access absent the individual's permission.
Encrypts or otherwise protects stored PII against unauthorized retrieval.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
CWE-359 does not impair RC.CO-04's ability to issue approved public recovery updates, yet any resulting PII exposure can partially undermine the outcome's overall efficacy and trust.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.5.34 only requires a policy, procedures, roles (e.g. privacy officer) and unspecified 'appropriate' measures; it does not itself stop unauthorized access to PII and depends on other controls (e.g. access enforcement) to do so, per the owner's explicit rule on dependency vs. effect.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Ubuntu 22.04 (1 rule)
- V-260531 Ubuntu 22.04 LTS must configure the SSH daemon to use FIPS 140-3-approved ciphers to prevent the unauthorized disclosure of information and/or detect changes to information during transmission. blocks CWE-359
Ubuntu 24.04 (1 rule)
- V-270670 Ubuntu 24.04 LTS must configure the SSH client to use FIPS 140-3 approved ciphers to prevent the unauthorized disclosure of information and/or detect changes to information during transmission. blocks CWE-359