{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22414 exists.","fix":"No fix has been published for CVE-2024-22414 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-22414 is a medium-severity cross-site scripting vulnerability in DogukanUrker flaskBlog, published on 17 Jan 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-22414 and fix it if it is affected.\n\nWhat it is: CVE-2024-22414 is a medium-severity cross-site scripting vulnerability in DogukanUrker flaskBlog, published on 17 Jan 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22414 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-2024-22414/ (Markdown: https://insights.sbomify.com/CVE-2024-22414/index.md)","id":"CVE-2024-22414","markdown":"https://insights.sbomify.com/CVE-2024-22414/index.md","name":"CVE-2024-22414","record":{"aliases":["GHSA-mrcw-j96f-p6v6"],"analysis":{"component_type":"web_application","fix_type":"workaround","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Flask blog application","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary JavaScript via stored comments in flaskBlog due to unsafe template rendering, requiring manual code modification to fix.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"flaskblog","vendor":"dogukanurker"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"flaskBlog is a simple blog app built with Flask. Improper storage and rendering of the `/user/\u003cuser\u003e` page allows a user's comments to execute arbitrary javascript code. The html template `user.html` contains the following code snippet to render comments made by a user: `\u003cdiv class=\"content\" tag=\"content\"\u003e{{comment[2]|safe}}\u003c/div\u003e`. Use of the \"safe\" tag causes flask to _not_ escape the rendered content. To remediate this, simply remove the `|safe` tag from the HTML above. No fix is is available and users are advised to manually edit their installation.","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":"User profile page vulnerable to Cross Site Scripting (XSS) in flaskBlog","id":"CVE-2024-22414","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Unsecured endpoints in the jupyter-lsp server extension","id":"CVE-2024-22415"},"packages":[],"prev":{"headline":"Further research determined the issue is not a vulnerability.","id":"CVE-2024-22413"},"products":["flaskBlog"],"published":"2024-01-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":"Cross-site request forgery in n/a","id":"CVE-2025-28101","kev_date_added":null,"published":"2025-04-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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["DogukanUrker"]},"summary":"Attackers can execute arbitrary JavaScript via stored comments in flaskBlog due to unsafe template rendering, requiring manual code modification to fix.","url":"https://insights.sbomify.com/CVE-2024-22414/"}