{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-28103 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-28103 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-28103 is a medium-severity missing authorization vulnerability in n/a, published on 21 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-28103 and fix it if it is affected.\n\nWhat it is: CVE-2025-28103 is a medium-severity missing authorization vulnerability in n/a, published on 21 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-28103 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-2025-28103/ (Markdown: https://insights.sbomify.com/CVE-2025-28103/index.md)","id":"CVE-2025-28103","markdown":"https://insights.sbomify.com/CVE-2025-28103/index.md","name":"CVE-2025-28103","record":{"aliases":["GHSA-87v4-c5h4-88xg"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"laskBlog","requires_auth":"low_privilege","summary":"Attackers can arbitrarily delete user accounts in laskBlog due to incorrect access control, requiring immediate attention from administrators.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flaskblog","vendor":"dogukanurker"}],"cvss":{"score":6.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Incorrect access control in laskBlog v2.6.1 allows attackers to arbitrarily delete user accounts via a crafted request.","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":"Missing authorization in n/a","id":"CVE-2025-28103","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-28104"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-28102"},"products":["n/a"],"published":"2025-04-21","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":"Cross-site request forgery in n/a","id":"CVE-2025-28101","kev_date_added":null,"published":"2025-04-17"},{"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"}],"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-05-12","vendors":["n/a"]},"summary":"Attackers can arbitrarily delete user accounts in laskBlog due to incorrect access control, requiring immediate attention from administrators.","url":"https://insights.sbomify.com/CVE-2025-28103/"}