{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-15215 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-15215 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-15215 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-15215 and fix it if it is affected.\n\nWhat it is: CVE-2017-15215 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-15215 in the wild and no public exploit code.\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-2017-15215/ (Markdown: https://insights.sbomify.com/CVE-2017-15215/index.md)","id":"CVE-2017-15215","markdown":"https://insights.sbomify.com/CVE-2017-15215/index.md","name":"CVE-2017-15215","record":{"aliases":["GHSA-jgj8-6rfv-fv92"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Shaarli link manager","requires_auth":"none","summary":"An unauthenticated attacker can inject JavaScript via the searchtags parameter, potentially taking over admin sessions or modifying settings.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"shaarli","vendor":"shaarli_project"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Reflected XSS vulnerability in Shaarli v0.9.1 allows an unauthenticated attacker to inject JavaScript via the searchtags parameter to index.php. If the victim is an administrator, an attacker can (for example) take over the admin session or change global settings or add/delete links. It is also possible to execute JavaScript against unauthenticated users.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2017-15215","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-15216"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-15214"},"products":["n/a"],"published":"2017-10-10","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2023-49469","kev_date_added":null,"published":"2023-12-28"},{"cvss_score":6.1,"headline":"Cross-site scripting in Shaarli","id":"CVE-2013-7351","kev_date_added":null,"published":"2020-01-02"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-5249","kev_date_added":null,"published":"2018-01-05"},{"cvss_score":5.3,"headline":"Shaarli vulnerable to stored XSS via Suggested Tags","id":"CVE-2026-24476","kev_date_added":null,"published":"2026-01-26"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"An unauthenticated attacker can inject JavaScript via the searchtags parameter, potentially taking over admin sessions or modifying settings.","url":"https://insights.sbomify.com/CVE-2017-15215/"}