{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-71454 exists.","exposure":"","fix":"No fix has been published for CVE-2025-71454 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-71454 is a medium-severity vulnerability in vtenext, published on 4 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2025-71454 and fix it if it is affected.\n\nWhat it is: CVE-2025-71454 is a medium-severity vulnerability in vtenext, published on 4 Nov 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-71454 exists.\n\nAffected product: vtenext. 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-71454/ (Markdown: https://insights.sbomify.com/CVE-2025-71454/index.md)","id":"CVE-2025-71454","markdown":"https://insights.sbomify.com/CVE-2025-71454/index.md","name":"CVE-2025-71454","record":{"aliases":["GHSA-28g9-rxcj-4j2q"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"vtenext before 25.02.2 contains a cross-site request forgery protection bypass because csrf_check() in include/utils/VteCsrf.php skips __csrf_token validation for non-POST requests. Attackers can induce a logged-in user to open a crafted link sending state-changing GET requests, which handlers read from $_REQUEST, performing actions as that user.","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":"vtenext before 25.02.2 CSRF Protection Bypass via HTTP Method Tampering","id":"CVE-2025-71454","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2025"},"n_packages":0,"n_references":4,"n_vendor_status":0,"next":{"headline":"vtenext before 25.02.2 Session Identifier Disclosure via Touch Web Service","id":"CVE-2025-71455"},"nickname":null,"packages":[],"prev":{"headline":"vtenext before 25.02.2 Reflected XSS via widgetInfoList in HomeWidgetBlockList","id":"CVE-2025-71453"},"products":["vtenext"],"published":"2026-11-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-11-05","vendor_status":[],"vendors":["vtenext"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-71454/"}