{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-2737 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-2737 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-2737 is a medium-severity cross-site scripting vulnerability in Unknown WP STAGING – Backup Duplicator \u0026 Migration, published on 16 Sep 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-2737 and fix it if it is affected.\n\nWhat it is: CVE-2022-2737 is a medium-severity cross-site scripting vulnerability in Unknown WP STAGING – Backup Duplicator \u0026 Migration, published on 16 Sep 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-2737 in the wild and no public exploit code.\n\nAffected product: Unknown WP STAGING – Backup Duplicator \u0026 Migration. 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-2022-2737/ (Markdown: https://insights.sbomify.com/CVE-2022-2737/index.md)","id":"CVE-2022-2737","markdown":"https://insights.sbomify.com/CVE-2022-2737/index.md","name":"CVE-2022-2737","record":{"aliases":["GHSA-4hxm-3749-gjx8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"High-privilege users can inject malicious scripts into WP STAGING settings, bypassing unfiltered_html restrictions in multisite environments.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp_staging","vendor":"wp-staging"}],"cvss":{"score":4.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The WP STAGING WordPress plugin before 2.9.18 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)","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":"WP STAGING \u003c 2.9.18 - Admin+ Stored Cross-Site Scripting","id":"CVE-2022-2737","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in podman","id":"CVE-2022-2738"},"packages":[],"prev":{"headline":"SourceCodester Company Website CMS Background Upload Logo Icon updatelogo.php unrestricted upload","id":"CVE-2022-2736"},"products":["WP STAGING – Backup Duplicator \u0026 Migration"],"published":"2022-09-16","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":"Migration Backup Restore \u003c 3.5.0 - Admin+ SSRF","id":"CVE-2024-4469","kev_date_added":null,"published":"2024-05-31"},{"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"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Unknown"]},"summary":"High-privilege users can inject malicious scripts into WP STAGING settings, bypassing unfiltered_html restrictions in multisite environments.","url":"https://insights.sbomify.com/CVE-2022-2737/"}