{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-1577 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-1577 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-1577 is a medium-severity vulnerability in Unknown Database Backup for WordPress, published on 6 Jun 2022. 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-1577 and fix it if it is affected.\n\nWhat it is: CVE-2022-1577 is a medium-severity vulnerability in Unknown Database Backup for WordPress, published on 6 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-1577 in the wild and no public exploit code.\n\nAffected product: Unknown Database Backup for WordPress. 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-1577/ (Markdown: https://insights.sbomify.com/CVE-2022-1577/index.md)","id":"CVE-2022-1577","markdown":"https://insights.sbomify.com/CVE-2022-1577/index.md","name":"CVE-2022-1577","record":{"aliases":["GHSA-r88p-mmpm-r9x8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick admins into changing backup settings via CSRF, potentially disabling backups or leaking notification emails.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"database_backup","vendor":"deliciousbrains"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Database Backup for WordPress plugin before 2.5.2 does not have CSRF check in place when updating the schedule backup settings, which could allow an attacker to make a logged in admin change them via a CSRF attack. This could lead to cases where attackers can send backup notification emails to themselves, which contain more details. Or disable the automatic backup schedule","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":"Database Backup for WordPress \u003c 2.5.2 - Arbitrary Schedule Settings Update via CSRF","id":"CVE-2022-1577","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"My wpdb \u003c 2.5 - Arbitrary SQL Query via CSRF","id":"CVE-2022-1578"},"packages":[],"prev":{"headline":"WP Maintenance Mode \u0026 Coming Soon \u003c 2.4.5 - Subscribed Users Deletion via CSRF","id":"CVE-2022-1576"},"products":["Database Backup for WordPress"],"published":"2022-06-06","related":[{"cvss_score":7.2,"headline":"Database Backup for WordPress \u003c 2.5.1 - Admin+ SQL Injection","id":"CVE-2022-0255","kev_date_added":null,"published":"2022-02-21"},{"cvss_score":5.4,"headline":"Database Backup for WordPress \u003c 2.4 - Authenticated Persistent Cross-Site Scripting (XSS)","id":"CVE-2021-24322","kev_date_added":null,"published":"2021-06-01"}],"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":"Attackers can trick admins into changing backup settings via CSRF, potentially disabling backups or leaking notification emails.","url":"https://insights.sbomify.com/CVE-2022-1577/"}