{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19725 exists.","fix":"No fix has been published for CVE-2026-19725 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-19725 is a critical path traversal vulnerability in Unknown WPvivid — Backup, Migration \u0026 Staging, published on 16 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-19725 and fix it if it is affected.\n\nWhat it is: CVE-2026-19725 is a critical path traversal vulnerability in Unknown WPvivid — Backup, Migration \u0026 Staging, published on 16 Aug 2026. 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-2026-19725 exists.\n\nAffected product: Unknown WPvivid — Backup, Migration \u0026 Staging. 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-2026-19725/ (Markdown: https://insights.sbomify.com/CVE-2026-19725/index.md)","id":"CVE-2026-19725","markdown":"https://insights.sbomify.com/CVE-2026-19725/index.md","name":"CVE-2026-19725","record":{"aliases":["GHSA-567f-mvhw-x8w5"],"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":"An attacker with a transfer key can create log files in arbitrary writable directories, including the web root, via path traversal.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The WPvivid — Backup, Migration \u0026 Staging WordPress plugin before 0.9.131 does not sanitise a value taken from an unauthenticated request before using it to build a log file path, allowing an attacker holding a site to site transfer key to create a log file in any existing writable directory of the site, including the web root.\n\nThe file name always carries a fixed suffix and the contents are always the WPvivid — Backup, Migration \u0026 Staging WordPress plugin before 0.9.131's own log header, so only the location of the file is attacker controlled.","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":"WPvivid Backup \u0026 Migration \u003c 0.9.131 - Unauthenticated Path Traversal via send_to_site_connect","id":"CVE-2026-19725","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Visualizer \u003c 4.0.7 - Contributor+ Cross-User Chart Configuration Disclosure","id":"CVE-2026-19726"},"packages":[],"prev":{"headline":"Social Media Share Buttons \u0026 Social Sharing Icons \u003c 3.0.1 - Reflected XSS via Pin It Share Handler","id":"CVE-2026-19723"},"products":["WPvivid — Backup, Migration \u0026 Staging"],"published":"2026-08-16","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-08-17","vendors":["Unknown"]},"summary":"An attacker with a transfer key can create log files in arbitrary writable directories, including the web root, via path traversal.","url":"https://insights.sbomify.com/CVE-2026-19725/"}