{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-28101 exists.","fix":"No fix has been published for CVE-2025-28101 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-28101 is a medium-severity vulnerability in n/a, published on 17 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-28101 and fix it if it is affected.\n\nWhat it is: CVE-2025-28101 is a medium-severity vulnerability in n/a, published on 17 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-28101 exists.\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-2025-28101/ (Markdown: https://insights.sbomify.com/CVE-2025-28101/index.md)","id":"CVE-2025-28101","markdown":"https://insights.sbomify.com/CVE-2025-28101/index.md","name":"CVE-2025-28101","record":{"aliases":["GHSA-mrgc-7pv6-7gc9"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Flask blog application","requires_auth":"none","summary":"Attackers can delete other users' blog posts via crafted requests due to missing CSRF protection in the Flask blog application.","user_interaction":"not_required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flaskblog","vendor":"dogukanurker"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"An arbitrary file deletion vulnerability in the /post/{postTitle} component of flaskBlog v2.6.1 allows attackers to delete article titles created by other users via supplying a crafted POST request.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-28101","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-28102"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-28100"},"products":["n/a"],"published":"2025-04-17","related":[{"cvss_score":9.3,"headline":"flaskBlog allows arbitrary privilege escalation","id":"CVE-2025-55736","kev_date_added":null,"published":"2025-08-19"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2025-28104","kev_date_added":null,"published":"2025-04-21"},{"cvss_score":6.9,"headline":"flaskBlo Authorization Bypass","id":"CVE-2025-55734","kev_date_added":null,"published":"2025-08-19"},{"cvss_score":6.9,"headline":"flaskBlog arbitrary comment delete","id":"CVE-2025-55737","kev_date_added":null,"published":"2025-08-19"},{"cvss_score":6.5,"headline":"User profile page vulnerable to Cross Site Scripting (XSS) in flaskBlog","id":"CVE-2024-22414","kev_date_added":null,"published":"2024-01-17"},{"cvss_score":6.4,"headline":"Missing authorization in n/a","id":"CVE-2025-28103","kev_date_added":null,"published":"2025-04-21"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-17","vendors":["n/a"]},"summary":"Attackers can delete other users' blog posts via crafted requests due to missing CSRF protection in the Flask blog application.","url":"https://insights.sbomify.com/CVE-2025-28101/"}