{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-57329 exists.","fix":"No fix has been published for CVE-2024-57329 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-57329 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Jan 2025. 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-57329 and fix it if it is affected.\n\nWhat it is: CVE-2024-57329 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Jan 2025. 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-57329 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-57329/ (Markdown: https://insights.sbomify.com/CVE-2024-57329/index.md)","id":"CVE-2024-57329","markdown":"https://insights.sbomify.com/CVE-2024-57329/index.md","name":"CVE-2024-57329","record":{"aliases":["GHSA-qcjj-7w9p-r3m9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"HortusFox plant management","requires_auth":"low_privilege","summary":"Attackers can inject arbitrary JavaScript via the plant name field, potentially leading to session hijacking or malicious actions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hortusfox","vendor":"hortusfox"}],"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":"HortusFox v3.9 contains a stored XSS vulnerability in the \"Add Plant\" function. The name input field does not sanitize or escape user inputs, allowing attackers to inject and execute arbitrary JavaScript payloads.","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":"Cross-site scripting in n/a","id":"CVE-2024-57329","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2024-57336"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2024-57328"},"products":["n/a"],"published":"2025-01-23","related":[{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2025-45317","kev_date_added":null,"published":"2025-08-13"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-45313","kev_date_added":null,"published":"2025-08-13"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-45314","kev_date_added":null,"published":"2025-08-13"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-45316","kev_date_added":null,"published":"2025-08-13"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2025-45315","kev_date_added":null,"published":"2025-08-13"}],"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-01-24","vendors":["n/a"]},"summary":"Attackers can inject arbitrary JavaScript via the plant name field, potentially leading to session hijacking or malicious actions.","url":"https://insights.sbomify.com/CVE-2024-57329/"}