{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11396 exists.","fix":"No fix has been published for CVE-2024-11396 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-11396 is a medium-severity vulnerability in awordpresslife Event Monster – Manager \u0026 Ticket Booking, published on 13 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-11396 and fix it if it is affected.\n\nWhat it is: CVE-2024-11396 is a medium-severity vulnerability in awordpresslife Event Monster – Manager \u0026 Ticket Booking, published on 13 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11396 exists.\n\nAffected product: awordpresslife Event Monster – Manager \u0026 Ticket Booking. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-11396/ (Markdown: https://insights.sbomify.com/CVE-2024-11396/index.md)","id":"CVE-2024-11396","markdown":"https://insights.sbomify.com/CVE-2024-11396/index.md","name":"CVE-2024-11396","record":{"aliases":["GHSA-6x4w-fvqp-6jvc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can access exported visitor data via a publicly accessible CSV file with a hardcoded filename.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"event_monster","vendor":"awplife"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-359","name":"Exposure of Private Personal Information to an Unauthorized Actor"}],"description":"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 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-01-13","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":1,"refs":[{"date":"2025-01-13T12:12:12Z","kind":"github_poc","ref":"https://github.com/RandomRobbieBF/CVE-2024-11396","stars":1,"title":"Event monster \u003c= 1.4.3 - Information Exposure Via Visitors List Export"},{"date":null,"kind":"nuclei","ref":"http/cves/2024/CVE-2024-11396.yaml","stars":null,"title":"Event Monster \u003c= 1.4.3 - Information Exposure Via Visitors List Export"}],"tier":"weaponised"},"has_fix":null,"headline":"Event monster \u003c= 1.4.3 - Information Exposure Via Visitors List Export","id":"CVE-2024-11396","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2024-11397"},"packages":[],"prev":{"headline":"Memory corruption in Chrome","id":"CVE-2024-11395"},"products":["Event Monster – Manager \u0026 Ticket Booking"],"published":"2025-01-13","related":[{"cvss_score":7.5,"headline":"Event Monster \u003c= 1.3.9 - Authenticated(Contributor+) PHP Object Injection via Custom Meta","id":"CVE-2024-1895","kev_date_added":null,"published":"2024-04-30"},{"cvss_score":7.2,"headline":"Event Monster \u003c 1.2.1 - Admin+ SQLi","id":"CVE-2022-3720","kev_date_added":null,"published":"2022-11-21"},{"cvss_score":5.9,"headline":"WordPress Event Management Tickets Booking Plugin \u003c= 1.3.2 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-47525","kev_date_added":null,"published":"2023-12-21"},{"cvss_score":5.3,"headline":"WordPress Event Monster Plugin \u003c= 1.4.0 - Sensitive Data Exposure vulnerability","id":"CVE-2024-5059","kev_date_added":null,"published":"2024-06-21"},{"cvss_score":4.3,"headline":"Event Monster \u003c 1.2.0 - Visitors Deletion via CSRF","id":"CVE-2022-3336","kev_date_added":null,"published":"2022-11-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["awordpresslife"]},"summary":"Unauthenticated attackers can access exported visitor data via a publicly accessible CSV file with a hardcoded filename.","url":"https://insights.sbomify.com/CVE-2024-11396/"}