{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-1895 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-1895 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-1895 is a high-severity unsafe deserialization vulnerability in awordpresslife Event Monster – Manager \u0026 Ticket Booking, published on 30 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-1895 and fix it if it is affected.\n\nWhat it is: CVE-2024-1895 is a high-severity unsafe deserialization vulnerability in awordpresslife Event Monster – Manager \u0026 Ticket Booking, published on 30 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-1895 in the wild and no public exploit code.\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-1895/ (Markdown: https://insights.sbomify.com/CVE-2024-1895/index.md)","id":"CVE-2024-1895","markdown":"https://insights.sbomify.com/CVE-2024-1895/index.md","name":"CVE-2024-1895","record":{"aliases":["GHSA-fv5j-c825-8pf5"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can exploit PHP object injection in the Event Monster plugin to potentially execute code or access data if a POP chain exists.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"event_monster","vendor":"awplife"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"The Event Monster – Event Management, Tickets Booking, Upcoming Event plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.3.9 via deserialization via shortcode of untrusted input from a custom meta value. This makes it possible for authenticated attackers, with contributor access and above, to inject a PHP Object. No POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Event Monster \u003c= 1.3.9 - Authenticated(Contributor+) PHP Object Injection via Custom Meta","id":"CVE-2024-1895","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Photo Gallery \u003c= 1.4.2 - Authenticated(Contributor+) PHP Object Injection via Shortcode","id":"CVE-2024-1896"},"packages":[],"prev":{"headline":"Cross-site scripting in Burst Statistics – Privacy-Friendly WordPress Analytics (Google Analytics Alternative)","id":"CVE-2024-1894"},"products":["Event Monster – Manager \u0026 Ticket Booking"],"published":"2024-04-30","related":[{"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":"Event monster \u003c= 1.4.3 - Information Exposure Via Visitors List Export","id":"CVE-2024-11396","kev_date_added":null,"published":"2025-01-13"},{"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["awordpresslife"]},"summary":"Authenticated contributors can exploit PHP object injection in the Event Monster plugin to potentially execute code or access data if a POP chain exists.","url":"https://insights.sbomify.com/CVE-2024-1895/"}