{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-7315 exists.","fix":"No fix has been published for CVE-2024-7315 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-7315 is a high-severity vulnerability in Unknown Migration, Backup, Staging, published on 2 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-7315 and fix it if it is affected.\n\nWhat it is: CVE-2024-7315 is a high-severity vulnerability in Unknown Migration, Backup, Staging, published on 2 Oct 2024. 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-2024-7315 exists.\n\nAffected product: Unknown Migration, Backup, 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-2024-7315/ (Markdown: https://insights.sbomify.com/CVE-2024-7315/index.md)","id":"CVE-2024-7315","markdown":"https://insights.sbomify.com/CVE-2024-7315/index.md","name":"CVE-2024-7315","record":{"aliases":["GHSA-g7xf-72mc-jx24"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can brute-force predictable backup filenames to access sensitive data in WPvivid plugin backups.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"migration\\,_backup\\,_staging","vendor":"wpvivid"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"The Migration, Backup, Staging  WordPress plugin before 0.9.106 does not use sufficient randomness in the filename that is created when generating a backup, which could be bruteforced by attackers to leak sensitive information about said backups.","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":"Migration, Backup, Staging – WPvivid \u003c 0.9.106 - Unauthenticated Sensitive Data Exposure","id":"CVE-2024-7315","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of Service (DoS) Vulnerability in Mitsubishi Electric CNC Series","id":"CVE-2024-7316"},"packages":[],"prev":{"headline":"anji-plus AJ-Report Authentication Bypass","id":"CVE-2024-7314"},"products":["Migration, Backup, Staging"],"published":"2024-10-02","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"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-27","vendors":["Unknown"]},"summary":"Attackers can brute-force predictable backup filenames to access sensitive data in WPvivid plugin backups.","url":"https://insights.sbomify.com/CVE-2024-7315/"}