{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4897 exists.","fix":"No fix has been published for CVE-2022-4897 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-4897 is a medium-severity cross-site scripting vulnerability in Unknown BackupBuddy, published on 21 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-4897 and fix it if it is affected.\n\nWhat it is: CVE-2022-4897 is a medium-severity cross-site scripting vulnerability in Unknown BackupBuddy, published on 21 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4897 exists.\n\nAffected product: Unknown BackupBuddy. 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-4897/ (Markdown: https://insights.sbomify.com/CVE-2022-4897/index.md)","id":"CVE-2022-4897","markdown":"https://insights.sbomify.com/CVE-2022-4897/index.md","name":"CVE-2022-4897","record":{"aliases":["GHSA-p8wr-66q2-pvj4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can inject malicious scripts via unsanitized parameters in BackupBuddy, potentially leading to session hijacking or code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"backupbuddy","vendor":"ithemes"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[],"description":"The BackupBuddy WordPress plugin before 8.8.3 does not sanitise and escape some parameters before outputting them back in various places, leading to Reflected Cross-Site Scripting","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2022/CVE-2022-4897.yaml","stars":null,"title":"WordPress BackupBuddy \u003c8.8.3 - Cross Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"BackupBuddy \u003c 8.8.3 - Multiple Reflected Cross-Site Scripting","id":"CVE-2022-4897","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in Octopus Server","id":"CVE-2022-4898"},"packages":[],"prev":{"headline":"Denial of service in Control de Ciber","id":"CVE-2022-4896"},"products":["BackupBuddy"],"published":"2023-02-21","related":[{"cvss_score":7.5,"headline":"WordPress BackupBuddy Plugin 8.5.8.0-8.7.4.1 is vulnerable to Directory Traversal","id":"CVE-2022-31474","kev_date_added":null,"published":"2023-03-13"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2013-2741","kev_date_added":null,"published":"2013-04-02"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2013-2742","kev_date_added":null,"published":"2013-04-02"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2013-2743","kev_date_added":null,"published":"2013-04-02"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2013-2744","kev_date_added":null,"published":"2013-04-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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-14","vendors":["Unknown"]},"summary":"Attackers can inject malicious scripts via unsanitized parameters in BackupBuddy, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2022-4897/"}