{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4469 exists.","fix":"No fix has been published for CVE-2024-4469 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-4469 is a high-severity server-side request forgery vulnerability in Unknown WP STAGING WordPress Backup Plugin , published on 31 May 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-4469 and fix it if it is affected.\n\nWhat it is: CVE-2024-4469 is a high-severity server-side request forgery vulnerability in Unknown WP STAGING WordPress Backup Plugin , published on 31 May 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-4469 exists.\n\nAffected product: Unknown WP STAGING WordPress Backup Plugin . 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-4469/ (Markdown: https://insights.sbomify.com/CVE-2024-4469/index.md)","id":"CVE-2024-4469","markdown":"https://insights.sbomify.com/CVE-2024-4469/index.md","name":"CVE-2024-4469","record":{"aliases":["GHSA-hw5v-77jj-prp8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress backup plugin","requires_auth":"none","summary":"Administrators can perform Server-Side Request Forgery attacks in multisite configurations, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp_staging","vendor":"wp-staging"}],"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-918","name":"Server-Side Request Forgery"}],"description":"The WP STAGING WordPress Backup Plugin  WordPress plugin before 3.5.0 does not prevent users with the administrator role from pinging conducting SSRF attacks, which may be a problem in multisite configurations.","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 Restore \u003c 3.5.0 - Admin+ SSRF","id":"CVE-2024-4469","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Master Slider – Responsive Touch Slider \u003c= 3.9.9 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2024-4470"},"packages":[],"prev":{"headline":"Salon booking system \u003c= 9.9 - Missing Authorization","id":"CVE-2024-4468"},"products":["WP STAGING WordPress Backup Plugin "],"published":"2024-05-31","related":[{"cvss_score":7.5,"headline":"WP STAGING PRO - Backup Duplicator \u0026 Migration \u003c= 5.6.0 - Cross-Site Request Forgery to Limited Local File Inclusion","id":"CVE-2024-5551","kev_date_added":null,"published":"2024-06-14"},{"cvss_score":7.5,"headline":"WP STAGING WordPress Backup Plugin \u003c 3.2.0 - Unauthorized Sensitive Data Exposure","id":"CVE-2023-7204","kev_date_added":null,"published":"2024-01-29"},{"cvss_score":7.5,"headline":"WP Staging (Free \u003c 3.1.3, Pro \u003c 5.1.3) - Unauthenticated Backup Download","id":"CVE-2023-6113","kev_date_added":null,"published":"2024-01-01"},{"cvss_score":4.8,"headline":"WP Staging \u003c 3.4.0, 5.4.0 (Pro Version) - Admin+ Stored XSS","id":"CVE-2024-2309","kev_date_added":null,"published":"2024-04-17"},{"cvss_score":4.8,"headline":"WP STAGING \u003c 2.9.18 - Admin+ Stored Cross-Site Scripting","id":"CVE-2022-2737","kev_date_added":null,"published":"2022-09-16"}],"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":"total"},"state":"PUBLISHED","updated":"2025-03-18","vendors":["Unknown"]},"summary":"Administrators can perform Server-Side Request Forgery attacks in multisite configurations, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2024-4469/"}