{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-22761 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-22761 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-22761 is a high-severity vulnerability in n/a, published on 29 Jul 2021. 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-2020-22761 and fix it if it is affected.\n\nWhat it is: CVE-2020-22761 is a high-severity vulnerability in n/a, published on 29 Jul 2021. 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-2020-22761 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2020-22761/ (Markdown: https://insights.sbomify.com/CVE-2020-22761/index.md)","id":"CVE-2020-22761","markdown":"https://insights.sbomify.com/CVE-2020-22761/index.md","name":"CVE-2020-22761","record":{"aliases":["GHSA-v4mc-gfxw-3c49"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"FlatPress CMS","requires_auth":"none","summary":"Attackers can trick authenticated users into deleting files in FlatPress via CSRF, requiring an upgrade to mitigate.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flatpress","vendor":"flatpress"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross Site Request Forgery (CSRF) vulnerability in FlatPress 1.1 via the DeleteFile function in flat/admin.php.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-22761","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"NukeViet Cross-site Scripting via the editor in the News module","id":"CVE-2020-22765"},"packages":[],"prev":{"headline":"MCMS vulnerable to arbitrary code execution via crafted thumbnail","id":"CVE-2020-22755"},"products":["n/a"],"published":"2021-07-29","related":[{"cvss_score":8.8,"headline":"PHP Remote File Inclusion in flatpressblog/flatpress","id":"CVE-2022-4606","kev_date_added":null,"published":"2022-12-18"},{"cvss_score":8.1,"headline":"Stored XSS in flatpressblog/flatpress","id":"CVE-2024-4023","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2024-41290","kev_date_added":null,"published":"2024-10-02"},{"cvss_score":8.1,"headline":"Cross-site Scripting (XSS) - Stored in flatpressblog/flatpress","id":"CVE-2023-1104","kev_date_added":null,"published":"2023-03-01"},{"cvss_score":8.1,"headline":"Path Traversal in flatpressblog/flatpress","id":"CVE-2023-0947","kev_date_added":null,"published":"2023-02-22"},{"cvss_score":8,"headline":"Cross-Site Request Forgery (CSRF) in flatpressblog/flatpress","id":"CVE-2024-9847","kev_date_added":null,"published":"2025-03-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can trick authenticated users into deleting files in FlatPress via CSRF, requiring an upgrade to mitigate.","url":"https://insights.sbomify.com/CVE-2020-22761/"}