{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1316 exists.","fix":"No fix has been published for CVE-2024-1316 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-1316 is a medium-severity vulnerability in Unknown Event Tickets and Registration, published on 4 Mar 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-1316 and fix it if it is affected.\n\nWhat it is: CVE-2024-1316 is a medium-severity vulnerability in Unknown Event Tickets and Registration, published on 4 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1316 exists.\n\nAffected product: Unknown Event Tickets and Registration. 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-1316/ (Markdown: https://insights.sbomify.com/CVE-2024-1316/index.md)","id":"CVE-2024-1316","markdown":"https://insights.sbomify.com/CVE-2024-1316/index.md","name":"CVE-2024-1316","record":{"aliases":["GHSA-wgfc-mmg5-p2xv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Contributors can leak the existence of private, draft, or protected events due to missing access controls in the Event Tickets plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"event_tickets","vendor":"liquidweb"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"The Event Tickets and Registration WordPress plugin before 5.8.1, Events Tickets Plus WordPress plugin before 5.9.1 does not prevent users with at least the contributor role from leaking the existence of certain events they shouldn't have access to. (e.g. draft, private, pending review, pw-protected, and trashed events).","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 Tickets and Registration \u003c 5.8.1 - Contributor+ Arbitrary Events Access","id":"CVE-2024-1316","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"RSS Aggregator by Feedzy \u003c= 4.4.2 - Authenticated(Contributor+) SQL Injection","id":"CVE-2024-1317"},"packages":[],"prev":{"headline":"Classified Listing \u003c= 3.0.4 - Cross-Site Request Forgery to Account Takeover via rtcl_update_user_account","id":"CVE-2024-1315"},"products":["Event Tickets and Registration","Events Tickets Plus"],"published":"2024-03-04","related":[{"cvss_score":8.8,"headline":"Other in n/a","id":"CVE-2019-16120","kev_date_added":null,"published":"2019-09-08"},{"cvss_score":5.3,"headline":"Event Tickets \u003c= 5.18.1 - Insecure Direct Object Reference to Sensitive Information Exposure","id":"CVE-2024-13457","kev_date_added":null,"published":"2025-01-30"},{"cvss_score":4.3,"headline":"Event Tickets Plus \u003c 5.9.1 - Contributor+ Attendees Lists Disclosure","id":"CVE-2024-1319","kev_date_added":null,"published":"2024-03-04"},{"cvss_score":4.3,"headline":"Event Tickets and Registration \u003c= 5.8.1 - Missing Authorization","id":"CVE-2024-1053","kev_date_added":null,"published":"2024-02-22"}],"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":"partial"},"state":"PUBLISHED","updated":"2024-08-28","vendors":["Unknown"]},"summary":"Contributors can leak the existence of private, draft, or protected events due to missing access controls in the Event Tickets plugin.","url":"https://insights.sbomify.com/CVE-2024-1316/"}