{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-7252 exists.","fix":"No fix has been published for CVE-2023-7252 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-7252 is a medium-severity missing authorization vulnerability in Unknown Tickera , published on 22 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-7252 and fix it if it is affected.\n\nWhat it is: CVE-2023-7252 is a medium-severity missing authorization vulnerability in Unknown Tickera , published on 22 Apr 2024. 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-2023-7252 exists.\n\nAffected product: Unknown Tickera . 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-2023-7252/ (Markdown: https://insights.sbomify.com/CVE-2023-7252/index.md)","id":"CVE-2023-7252","markdown":"https://insights.sbomify.com/CVE-2023-7252/index.md","name":"CVE-2023-7252","record":{"aliases":["GHSA-6cxj-fx46-x5rx"],"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":"Attackers can access other users' tickets due to missing authorization checks in the Tickera WordPress plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"tickera","vendor":"tickera"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[],"description":"The Tickera  WordPress plugin before 3.5.2.5 does not prevent users from leaking other users' tickets.","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":"Tickera \u003c 3.5.2.5 - Ticket leakage through IDOR","id":"CVE-2023-7252","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Import WP \u003c 2.13.1 - Admin+ Server-side Request Forgery","id":"CVE-2023-7253"},"packages":[],"prev":{"headline":"WordPress User Submitted Posts plugin \u003c= 20230901 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2023-7251"},"products":["Tickera "],"published":"2024-04-22","related":[{"cvss_score":7.3,"headline":"Tickera – WordPress Event Ticketing \u003c= 3.5.4.4 - Unauthenticated Arbitrary Shortcode Execution","id":"CVE-2024-10263","kev_date_added":null,"published":"2024-11-05"},{"cvss_score":6.1,"headline":"Tickera \u003c 3.4.8.3 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2021-24797","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":5.3,"headline":"WordPress Tickera plugin \u003c= 3.5.2.6 - Broken Access Control vulnerability","id":"CVE-2024-35729","kev_date_added":null,"published":"2024-06-10"},{"cvss_score":4.3,"headline":"Tickera \u003c= 3.5.2.8 - Missing Authorization to Authenticated (Susbcriber+) Ticket Deletion","id":"CVE-2024-5860","kev_date_added":null,"published":"2024-06-18"},{"cvss_score":4.3,"headline":"Tickera \u003c 3.5.1.0 - Plugin Data Deletion via CSRF","id":"CVE-2022-4549","kev_date_added":null,"published":"2023-01-16"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-22","vendors":["Unknown"]},"summary":"Attackers can access other users' tickets due to missing authorization checks in the Tickera WordPress plugin.","url":"https://insights.sbomify.com/CVE-2023-7252/"}