{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90931 exists.","fix":"No fix has been published for CVE-2026-90931 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-90931 is a medium-severity cross-site scripting vulnerability in laradashboard, published on 14 Sep 2026. 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-2026-90931 and fix it if it is affected.\n\nWhat it is: CVE-2026-90931 is a medium-severity cross-site scripting vulnerability in laradashboard, published on 14 Sep 2026. 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-2026-90931 exists.\n\nAffected product: laradashboard. 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-90931/ (Markdown: https://insights.sbomify.com/CVE-2026-90931/index.md)","id":"CVE-2026-90931","markdown":"https://insights.sbomify.com/CVE-2026-90931/index.md","name":"CVE-2026-90931","record":{"aliases":["GHSA-9gxw-qpx8-x9c7","GHSA-qxqf-9qjp-qgw3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"LaraDashboard","requires_auth":"low_privilege","summary":"Authenticated users can upload malicious SVG files to execute scripts in admin sessions, leading to account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/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":"LaraDashboard versions 0.9.0 through 1.2.2 fail to sanitize SVG file content during media upload, allowing authenticated users with only the media.create permission to upload malicious SVG files containing script tags. When any user including administrators opens the stored SVG file served inline from the application origin, the embedded JavaScript executes in the dashboard context, enabling session hijacking and administrative account takeover.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-10-26","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-26T23:39:24Z","kind":"github_poc","ref":"https://github.com/capivara-research/CVE-2026-90931","stars":0,"title":"CVE-2026-90931: LaraDashboard stored XSS via SVG upload — bilingual analysis and safe PoC"}],"tier":"weaponised"},"has_fix":false,"headline":"LaraDashboard 0.9.0 through 1.2.2 Stored XSS via SVG Upload","id":"CVE-2026-90931","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"LaraDashboard 0.9.2 through 1.2.2 Path Traversal RCE","id":"CVE-2026-90932"},"packages":[],"prev":{"headline":"File Browser through 2.63.23 Path Traversal via Symlink Alias","id":"CVE-2026-90930"},"products":["laradashboard"],"published":"2026-09-14","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["laradashboard"]},"summary":"Authenticated users can upload malicious SVG files to execute scripts in admin sessions, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2026-90931/"}