{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-41021 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-41021 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-41021 is a medium-severity cross-site scripting vulnerability in Sergestec SISTICK, published on 16 Oct 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-2025-41021 and fix it if it is affected.\n\nWhat it is: CVE-2025-41021 is a medium-severity cross-site scripting vulnerability in Sergestec SISTICK, published on 16 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-41021 in the wild and no public exploit code.\n\nAffected product: Sergestec SISTICK. 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-41021/ (Markdown: https://insights.sbomify.com/CVE-2025-41021/index.md)","id":"CVE-2025-41021","markdown":"https://insights.sbomify.com/CVE-2025-41021/index.md","name":"CVE-2025-41021","record":{"aliases":["GHSA-7xc6-7q94-gh44"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Sergestec Exito","requires_auth":"low_privilege","summary":"Stored XSS in Sergestec Exito allows attackers to steal session cookies from authenticated users via the product update form.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCIBE","cpe":[{"product":"exito","vendor":"sergestec"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Stored Cross-Site Scripting (XSS) in Sergestec's Exito v8.0, consisting of a stored XSS due to a lack of proper validation of user input by sending a POST request using the 'obs' parameter in '/admin/index.php?action=product_update'. This vulnerability could allow a remote user to send a specially crafted query to an authenticated user and steal their cookie session details.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Stored Cross-Site Scripting (XSS) vulnerability in Sergestec's Exito","id":"CVE-2025-41021","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Authentication bypass in AutoGPT de Thesamur","id":"CVE-2025-41023"},"packages":[],"prev":{"headline":"Insecure direct object reference (IDOR) vulnerability in Sergestec's Exito","id":"CVE-2025-41020"},"products":["SISTICK"],"published":"2025-10-16","related":[{"cvss_score":9.3,"headline":"SQL injection vulnerability in Sergestec's Exito","id":"CVE-2025-41018","kev_date_added":null,"published":"2025-10-16"},{"cvss_score":7.1,"headline":"Insecure direct object reference (IDOR) vulnerability in Sergestec's Exito","id":"CVE-2025-41020","kev_date_added":null,"published":"2025-10-16"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-16","vendors":["Sergestec"]},"summary":"Stored XSS in Sergestec Exito allows attackers to steal session cookies from authenticated users via the product update form.","url":"https://insights.sbomify.com/CVE-2025-41021/"}