{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22549 exists.","fix":"No fix has been published for CVE-2024-22549 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-22549 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 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-22549 and fix it if it is affected.\n\nWhat it is: CVE-2024-22549 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 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-22549 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-2024-22549/ (Markdown: https://insights.sbomify.com/CVE-2024-22549/index.md)","id":"CVE-2024-22549","markdown":"https://insights.sbomify.com/CVE-2024-22549/index.md","name":"CVE-2024-22549","record":{"aliases":["GHSA-w4p6-8j24-xpq3"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"FlyCms","requires_auth":"low_privilege","summary":"An attacker can inject malicious scripts into the email settings of FlyCms, potentially leading to session hijacking or code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flycms","vendor":"flycms_project"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"FlyCms 1.0 is vulnerable to Cross Site Scripting (XSS) in the email settings of the website settings section.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2024-22549","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2024-22550"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-22548"},"products":["n/a"],"published":"2024-01-18","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-22568","kev_date_added":null,"published":"2024-01-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-22591","kev_date_added":null,"published":"2024-01-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-22592","kev_date_added":null,"published":"2024-01-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-22593","kev_date_added":null,"published":"2024-01-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-22601","kev_date_added":null,"published":"2024-01-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-22603","kev_date_added":null,"published":"2024-01-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-22699","kev_date_added":null,"published":"2024-01-18"}],"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-20","vendors":["n/a"]},"summary":"An attacker can inject malicious scripts into the email settings of FlyCms, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2024-22549/"}