{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55736 exists.","fix":"No fix has been published for CVE-2025-55736 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55736 is a critical vulnerability in DogukanUrker FlaskBlog, published on 19 Aug 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-55736 and fix it if it is affected.\n\nWhat it is: CVE-2025-55736 is a critical vulnerability in DogukanUrker FlaskBlog, published on 19 Aug 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-55736 exists.\n\nAffected product: DogukanUrker FlaskBlog. 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-55736/ (Markdown: https://insights.sbomify.com/CVE-2025-55736/index.md)","id":"CVE-2025-55736","markdown":"https://insights.sbomify.com/CVE-2025-55736/index.md","name":"CVE-2025-55736","record":{"aliases":["GHSA-6q83-vfmq-wf72"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Flask blog application","requires_auth":"none","summary":"An arbitrary user can escalate privileges to admin by modifying their role, allowing them to delete users, posts, and comments.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"flaskblog","vendor":"dogukanurker"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-807","name":"Reliance on Untrusted Inputs in a Security Decision"},{"id":"CWE-425","name":"Direct Request"}],"description":"flaskBlog is a blog app built with Flask. In 2.8.0 and earlier, an arbitrary user can change his role to \"admin\", giving its relative privileges (e.g. delete users, posts, comments etc.). The problem is in the routes/adminPanelUsers file.","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":"flaskBlog allows arbitrary privilege escalation","id":"CVE-2025-55736","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"flaskBlog arbitrary comment delete","id":"CVE-2025-55737"},"packages":[],"prev":{"headline":"flaskBlog Stored XSS Vulnerability","id":"CVE-2025-55735"},"products":["FlaskBlog"],"published":"2025-08-19","related":[{"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"},{"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-08-19","vendors":["DogukanUrker"]},"summary":"An arbitrary user can escalate privileges to admin by modifying their role, allowing them to delete users, posts, and comments.","url":"https://insights.sbomify.com/CVE-2025-55736/"}