{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-27189 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-27189 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27189 is a medium-severity vulnerability in Adobe Commerce B2b, published on 8 Apr 2025. 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-2025-27189 and fix it if it is affected.\n\nWhat it is: CVE-2025-27189 is a medium-severity vulnerability in Adobe Commerce B2b, published on 8 Apr 2025. 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-2025-27189 in the wild and no public exploit code.\n\nAffected product: Adobe Commerce B2b. 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-2025-27189/ (Markdown: https://insights.sbomify.com/CVE-2025-27189/index.md)","id":"CVE-2025-27189","markdown":"https://insights.sbomify.com/CVE-2025-27189/index.md","name":"CVE-2025-27189","record":{"aliases":["GHSA-fpf8-39f6-cgrc"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Adobe Commerce","requires_auth":"none","summary":"Attackers can trick logged-in users into submitting forged requests, causing a denial-of-service condition in Adobe Commerce.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"adobe","cpe":[{"product":"commerce_b2b","vendor":"adobe"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Adobe Commerce versions 2.4.7-p4, 2.4.6-p9, 2.4.5-p11, 2.4.4-p12, 2.4.8-beta2 and earlier are affected by a Cross-Site Request Forgery (CSRF) vulnerability that could be exploited to cause a denial-of-service condition. An attacker could trick a logged-in user into submitting a forged request to the vulnerable application, which may disrupt service availability. Exploitation of this issue requires user interaction, typically in the form of clicking a malicious link or visiting an attacker-controlled website.","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":"Adobe Commerce | Cross-Site Request Forgery (CSRF) (CWE-352)","id":"CVE-2025-27189","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"adobe:commerce_b2b","products":["adobe:commerce_b2b"],"type":"csrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Adobe Commerce | Improper Access Control (CWE-284)","id":"CVE-2025-27190"},"packages":[],"prev":{"headline":"Adobe Commerce | Incorrect Authorization (CWE-863)","id":"CVE-2025-27188"},"products":["Adobe Commerce"],"published":"2025-04-08","related":[{"cvss_score":8.1,"headline":"Adobe Commerce | Improper Authorization (CWE-285)","id":"CVE-2025-24418","kev_date_added":null,"published":"2025-02-11"},{"cvss_score":7.1,"headline":"Adobe Commerce | Incorrect Authorization (CWE-863)","id":"CVE-2025-24407","kev_date_added":null,"published":"2025-02-11"},{"cvss_score":6.5,"headline":"Adobe Commerce | Improper Access Control (CWE-284)","id":"CVE-2025-27207","kev_date_added":null,"published":"2025-06-10"},{"cvss_score":6.5,"headline":"Adobe Commerce | Improper Access Control (CWE-284)","id":"CVE-2025-24422","kev_date_added":null,"published":"2025-02-11"},{"cvss_score":6.5,"headline":"Adobe Commerce | Improper Access Control (CWE-284)","id":"CVE-2025-24424","kev_date_added":null,"published":"2025-02-11"},{"cvss_score":6.5,"headline":"Adobe Commerce | Improper Access Control (CWE-284)","id":"CVE-2025-24426","kev_date_added":null,"published":"2025-02-11"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-08","vendors":["Adobe"]},"summary":"Attackers can trick logged-in users into submitting forged requests, causing a denial-of-service condition in Adobe Commerce.","url":"https://insights.sbomify.com/CVE-2025-27189/"}