{"answers":{"affected":"2 open source packages ship an affected version, including anchorcms/anchor-cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-25576 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-25576 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25576 is a medium-severity vulnerability in n/a, published on 24 Mar 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-25576 and fix it if it is affected.\n\nWhat it is: CVE-2022-25576 is a medium-severity vulnerability in n/a, published on 24 Mar 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-25576 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- anchorcms/anchor-cms (Packagist): affected all versions up to 0.12.7; no fix listed\n- anchorcms/anchor-cms (Packagist): affected all versions up to 0.12.7; no fix listed\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-25576/ (Markdown: https://insights.sbomify.com/CVE-2022-25576/index.md)","id":"CVE-2022-25576","markdown":"https://insights.sbomify.com/CVE-2022-25576/index.md","name":"CVE-2022-25576","record":{"aliases":["GHSA-322v-p3jc-7hrg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Anchor CMS","requires_auth":"high_privilege","summary":"Attackers can exploit CSRF in Anchor CMS to arbitrarily delete posts, requiring user interaction to trigger the malicious action.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"anchor_cms","vendor":"anchorcms"}],"cvss":{"score":4.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Anchor CMS v0.12.7 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component anchor/routes/posts.php. This vulnerability allows attackers to arbitrarily delete posts.","ecosystems":["Packagist"],"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 Anchor CMS","id":"CVE-2022-25576","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-25577"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["0.12.7"],"package":"anchorcms/anchor-cms","purl":null,"source":"GHSA-322v-p3jc-7hrg"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["0.12.7"],"package":"anchorcms/anchor-cms","purl":"pkg:composer/anchorcms/anchor-cms","source":"GHSA-322v-p3jc-7hrg"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-25575"},"products":["n/a"],"published":"2022-03-24","related":[{"cvss_score":8.8,"headline":"Cross-site scripting in n/a","id":"CVE-2024-37732","kev_date_added":null,"published":"2024-06-24"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-23342","kev_date_added":null,"published":"2021-01-19"},{"cvss_score":7.5,"headline":"Deserialization in n/a","id":"CVE-2015-5687","kev_date_added":null,"published":"2015-10-05"},{"cvss_score":7.4,"headline":"Cross-Site Request Forgery in Anchor CMS","id":"CVE-2024-29499","kev_date_added":null,"published":"2024-03-22"},{"cvss_score":6.1,"headline":"Cross-site Scripting in Anchor CMS","id":"CVE-2021-44116","kev_date_added":null,"published":"2021-12-15"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2015-5060","kev_date_added":null,"published":"2017-09-07"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2025-46041","kev_date_added":null,"published":"2025-06-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":["n/a"]},"summary":"Attackers can exploit CSRF in Anchor CMS to arbitrarily delete posts, requiring user interaction to trigger the malicious action.","url":"https://insights.sbomify.com/CVE-2022-25576/"}