{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3720 exists.","fix":"No fix has been published for CVE-2022-3720 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-3720 is a high-severity SQL injection vulnerability in Unknown Event Monster, published on 21 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-3720 and fix it if it is affected.\n\nWhat it is: CVE-2022-3720 is a high-severity SQL injection vulnerability in Unknown Event Monster, published on 21 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3720 exists.\n\nAffected product: Unknown Event Monster. 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-2022-3720/ (Markdown: https://insights.sbomify.com/CVE-2022-3720/index.md)","id":"CVE-2022-3720","markdown":"https://insights.sbomify.com/CVE-2022-3720/index.md","name":"CVE-2022-3720","record":{"aliases":["GHSA-v727-m7g4-8xpx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"High-privilege users can exploit SQL injection in the Event Monster WordPress plugin to read or modify database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"event_monster","vendor":"awplife"}],"cvss":{"score":7.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"The Event Monster WordPress plugin before 1.2.0 does not validate and escape some parameters before using them in SQL statements, which could lead to SQL Injection exploitable by high privilege users","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Event Monster \u003c 1.2.1 - Admin+ SQLi","id":"CVE-2022-3720","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Code Injection in froxlor/froxlor","id":"CVE-2022-3721"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2022-3719"},"products":["Event Monster"],"published":"2022-11-21","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":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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-30","vendors":["Unknown"]},"summary":"High-privilege users can exploit SQL injection in the Event Monster WordPress plugin to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2022-3720/"}