{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-4637 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-4637 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-4637 is a medium-severity missing authorization vulnerability in wpvividplugins WPvivid — Backup, Migration \u0026 Staging, published on 5 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-4637 and fix it if it is affected.\n\nWhat it is: CVE-2023-4637 is a medium-severity missing authorization vulnerability in wpvividplugins WPvivid — Backup, Migration \u0026 Staging, published on 5 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-4637 in the wild and no public exploit code.\n\nAffected product: wpvividplugins 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-2023-4637/ (Markdown: https://insights.sbomify.com/CVE-2023-4637/index.md)","id":"CVE-2023-4637","markdown":"https://insights.sbomify.com/CVE-2023-4637/index.md","name":"CVE-2023-4637","record":{"aliases":["GHSA-3qmf-fj65-6vmf"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Unauthenticated attackers can obtain full file paths by invoking restore functions if they possess a backup ID.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"migration\\,_backup\\,_staging","vendor":"wpvivid"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The WPvivid plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the restore() and get_restore_progress() function in versions up to, and including, 0.9.94. This makes it possible for unauthenticated attackers to invoke these functions and obtain full file paths if they have access to a back-up ID.","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":"WPvivid \u003c= 0.9.94 - Missing Authorization","id":"CVE-2023-4637","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Undertow: cookie smuggling/spoofing","id":"CVE-2023-4639"},"packages":[],"prev":{"headline":"WordPress File Sharing Plugin \u003c= 2.0.3 - Authenticated (Admin+) Stored Cross-Site Scripting","id":"CVE-2023-4636"},"products":["WPvivid — Backup, Migration \u0026 Staging"],"published":"2024-02-05","related":[{"cvss_score":9.8,"headline":"SQL injection in Migration, Backup, Staging – WPvivid","id":"CVE-2024-1981","kev_date_added":null,"published":"2024-02-29"},{"cvss_score":8.8,"headline":"Migration, Backup, Staging – WPvivid \u003c= 0.9.107 - Unauthenticated PHP Object Injection","id":"CVE-2024-10962","kev_date_added":null,"published":"2024-11-14"},{"cvss_score":8.8,"headline":"Migration, Backup, Staging – WPvivid \u003c= 0.9.35 - Authenticated (Subscriber+) Arbitrary File Upload","id":"CVE-2020-36842","kev_date_added":null,"published":"2024-10-16"},{"cvss_score":8.8,"headline":"WordPress WPvivid Backup Plugin plugin \u003c= 0.9.90 - Privilege Escalation on Staging Environment vulnerability","id":"CVE-2023-41243","kev_date_added":null,"published":"2024-05-17"},{"cvss_score":8.7,"headline":"Path traversal in Migration, Backup, Staging – WPvivid","id":"CVE-2023-4274","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":8,"headline":"Migration, Backup, Staging – WPvivid \u003c= 0.9.91 - Google Drive Client Secret Exposure","id":"CVE-2023-5576","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":7.5,"headline":"Migration, Backup, Staging – WPvivid \u003c 0.9.106 - Unauthenticated Sensitive Data Exposure","id":"CVE-2024-7315","kev_date_added":null,"published":"2024-10-02"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["wpvividplugins"]},"summary":"Unauthenticated attackers can obtain full file paths by invoking restore functions if they possess a backup ID.","url":"https://insights.sbomify.com/CVE-2023-4637/"}