{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48823 exists.","fix":"No fix has been published for CVE-2026-48823 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-48823 is a medium-severity cross-site scripting vulnerability in Shaarli, published on 17 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-48823 and fix it if it is affected.\n\nWhat it is: CVE-2026-48823 is a medium-severity cross-site scripting vulnerability in Shaarli, published on 17 Jun 2026. It can only be exploited from the same machine or local 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-2026-48823 exists.\n\nAffected product: Shaarli. 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-2026-48823/ (Markdown: https://insights.sbomify.com/CVE-2026-48823/index.md)","id":"CVE-2026-48823","markdown":"https://insights.sbomify.com/CVE-2026-48823/index.md","name":"CVE-2026-48823","record":{"aliases":["DEBIAN-CVE-2026-48823","GHSA-68qr-fvv8-6mc6","UBUNTU-CVE-2026-48823"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Personal bookmarking service","requires_auth":"high_privilege","summary":"Authenticated users can inject JavaScript via tags, leading to stored XSS when others use the tag filter, risking session hijacking or data theft.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Shaarli is a personal bookmarking service. Versions 0.16.1 and prior contain a stored Cross-Site Scripting (XSS) vulnerability in the tag filtering functionality of Shaarli. An authenticated user can inject arbitrary JavaScript into the tags field when creating a bookmark (Shaare). The malicious payload is stored and later executed when users interact with the \"Filter by tag\" search feature on the homepage. User-supplied input in the tags field is not properly sanitized or output-escaped before being rendered in the tag filtering interface. When a bookmark is created with a malicious payload inside the tag field, the payload is stored in the database. Later, when a user searches using the \"Filter by tag\" functionality on the homepage, the application renders matching tags dynamically. If the tag value contains HTML with JavaScript event handlers, it is injected into the DOM. This impacts anyone interacting with the \"Filter by tag\" search functionality, administrators and privileged users. This issue has been fixed in version 0.16.2.","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":"Shaarli has Stored Cross-Site Scripting (XSS) via Tags Search","id":"CVE-2026-48823","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Mailpit: Sibling-endpoint memory-exhaustion DoS via unbounded JSON body on /api/v1/messages, /api/v1/tags, and /api/v1/message/{id}/release (incomplete fix of GHSA-fpxj-m5q8-fphw)","id":"CVE-2026-48824"},"packages":[],"prev":{"headline":"Shaarli has Stored Cross-Site Scripting (XSS) via Markdown Reference Links","id":"CVE-2026-48822"},"products":["Shaarli"],"published":"2026-06-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-06-18","vendors":["shaarli"]},"summary":"Authenticated users can inject JavaScript via tags, leading to stored XSS when others use the tag filter, risking session hijacking or data theft.","url":"https://insights.sbomify.com/CVE-2026-48823/"}