{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1762 exists.","fix":"No fix has been published for CVE-2025-1762 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1762 is a medium-severity vulnerability in Unknown Event Tickets with Ticket Scanner, published on 28 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-1762 and fix it if it is affected.\n\nWhat it is: CVE-2025-1762 is a medium-severity vulnerability in Unknown Event Tickets with Ticket Scanner, published on 28 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1762 exists.\n\nAffected product: Unknown Event Tickets with Ticket Scanner. 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-2025-1762/ (Markdown: https://insights.sbomify.com/CVE-2025-1762/index.md)","id":"CVE-2025-1762","markdown":"https://insights.sbomify.com/CVE-2025-1762/index.md","name":"CVE-2025-1762","record":{"aliases":["GHSA-475h-5v9w-xfp6"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick logged-in admins into deleting arbitrary tickets via CSRF, requiring an upgrade to the Event Tickets with Ticket Scanner plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"event_tickets_with_ticket_scanner","vendor":"vollstart"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Event Tickets with Ticket Scanner WordPress plugin before 2.5.4 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack","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 with Ticket Scanner \u003c 2.5.4 - Arbitrary Tickets Deletion via CSRF","id":"CVE-2025-1762","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab","id":"CVE-2025-1763"},"packages":[],"prev":{"headline":"IBM Concert Software information disclosure","id":"CVE-2025-1761"},"products":["Event Tickets with Ticket Scanner"],"published":"2025-03-28","related":[{"cvss_score":9.9,"headline":"WordPress Event Tickets with Ticket Scanner plugin \u003c= 2.3.11 - Remote Code Execution (RCE) vulnerability","id":"CVE-2024-52427","kev_date_added":null,"published":"2024-11-18"},{"cvss_score":7.1,"headline":"WordPress Event Tickets with Ticket Scanner plugin \u003c= 2.3.1 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-35652","kev_date_added":null,"published":"2024-06-04"},{"cvss_score":3.5,"headline":"Event Tickets with Ticket Scanner \u003c 2.3.8 - Admin+ Stored XSS","id":"CVE-2024-6711","kev_date_added":null,"published":"2025-05-15"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-28","vendors":["Unknown"]},"summary":"Attackers can trick logged-in admins into deleting arbitrary tickets via CSRF, requiring an upgrade to the Event Tickets with Ticket Scanner plugin.","url":"https://insights.sbomify.com/CVE-2025-1762/"}