{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-71457 exists.","exposure":"","fix":"No fix has been published for CVE-2025-71457 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-71457 is a critical vulnerability in vtenext, published on 4 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2025-71457 and fix it if it is affected.\n\nWhat it is: CVE-2025-71457 is a critical 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-71457 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-71457/ (Markdown: https://insights.sbomify.com/CVE-2025-71457/index.md)","id":"CVE-2025-71457","markdown":"https://insights.sbomify.com/CVE-2025-71457/index.md","name":"CVE-2025-71457","record":{"aliases":["GHSA-v286-fq46-38fw"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-620","name":"Unverified Password Change"}],"description":"vtenext 25.02 before 25.02.1 contains an authentication bypass vulnerability that allows unauthenticated attackers to change any account password via hub/rpwd.php without token verification. Attackers knowing a valid user_name can send action=change_password to RecoverPwd::displayChangePwd() and log in as administrators lacking two-factor authentication.","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 25.02 before 25.02.1 Unverified Password Change via hub/rpwd.php","id":"CVE-2025-71457","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":"FTS3 Web Monitoring 3.12.0 through 3.13.2 and 3.14.0 SQL Injection via /linkinfo","id":"CVE-2025-71458"},"nickname":null,"packages":[],"prev":{"headline":"vtenext before 25.02.2 SQL Injection via fieldname in Fax EditView","id":"CVE-2025-71456"},"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-11-05","vendor_status":[],"vendors":["vtenext"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-71457/"}