{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-46462 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-46462 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46462 is a medium-severity vulnerability in Trân Minh-Quân WPVN, published on 24 Apr 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-46462 and fix it if it is affected.\n\nWhat it is: CVE-2025-46462 is a medium-severity vulnerability in Trân Minh-Quân WPVN, published on 24 Apr 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: There is no known exploitation of CVE-2025-46462 in the wild and no public exploit code.\n\nAffected product: Trân Minh-Quân WPVN. 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-46462/ (Markdown: https://insights.sbomify.com/CVE-2025-46462/index.md)","id":"CVE-2025-46462","markdown":"https://insights.sbomify.com/CVE-2025-46462/index.md","name":"CVE-2025-46462","record":{"aliases":["GHSA-hvmx-fwxj-5h9p"],"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 users into changing their username via CSRF, requiring plugin updates to mitigate.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","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":"Cross-Site Request Forgery (CSRF) vulnerability in Trân Minh-Quân WPVN wpvn-username-changer allows Cross Site Request Forgery.This issue affects WPVN: from n/a through \u003c= 0.7.8.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WordPress WPVN plugin \u003c= 0.7.8 - Cross Site Request Forgery (CSRF) Vulnerability","id":"CVE-2025-46462","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Mailing Group Listserv plugin \u003c= 3.0.4 - SQL Injection Vulnerability","id":"CVE-2025-46463"},"packages":[],"prev":{"headline":"WordPress RRSSB plugin \u003c= 1.0.1 - Cross Site Scripting (XSS) Vulnerability","id":"CVE-2025-46461"},"products":["WPVN"],"published":"2025-04-24","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["Trân Minh-Quân"]},"summary":"Attackers can trick users into changing their username via CSRF, requiring plugin updates to mitigate.","url":"https://insights.sbomify.com/CVE-2025-46462/"}