{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-44919 exists.","fix":"No fix has been published for CVE-2024-44919 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-44919 is a medium-severity cross-site scripting vulnerability in Seacms Seacms, published on 29 Aug 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-44919 and fix it if it is affected.\n\nWhat it is: CVE-2024-44919 is a medium-severity cross-site scripting vulnerability in Seacms Seacms, published on 29 Aug 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-44919 exists.\n\nAffected product: Seacms Seacms. 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-44919/ (Markdown: https://insights.sbomify.com/CVE-2024-44919/index.md)","id":"CVE-2024-44919","markdown":"https://insights.sbomify.com/CVE-2024-44919/index.md","name":"CVE-2024-44919","record":{"aliases":["GHSA-q777-ff33-4xgr"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SeaCMS","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary web scripts via XSS in SeaCMS admin ad description field, potentially compromising admin sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"seacms","vendor":"seacms"}],"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":"A cross-site scripting (XSS) vulnerability in the component admin_ads.php of SeaCMS v12.9 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the ad description parameter.","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-44919","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"seacms:seacms","products":["seacms:seacms"],"type":"xss","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-44920"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-44918"},"products":["n/a"],"published":"2024-08-29","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-44073","kev_date_added":null,"published":"2025-05-06"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2025-44071","kev_date_added":null,"published":"2025-05-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-44072","kev_date_added":null,"published":"2025-05-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-44074","kev_date_added":null,"published":"2025-05-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-29647","kev_date_added":null,"published":"2025-04-03"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-25516","kev_date_added":null,"published":"2025-02-25"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-25517","kev_date_added":null,"published":"2025-02-25"}],"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":"2024-08-30","vendors":["n/a"]},"summary":"Attackers can execute arbitrary web scripts via XSS in SeaCMS admin ad description field, potentially compromising admin sessions.","url":"https://insights.sbomify.com/CVE-2024-44919/"}