{"answers":{"affected":"2 open source packages ship an affected version, including flarum/nicknames.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30913 exists.","fix":"Upgrade flarum/nicknames to 1.8.3 or later.","what":"CVE-2026-30913 is a medium-severity cross-site scripting vulnerability in flarum nicknames, published on 9 Mar 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-30913 and fix it if it is affected.\n\nWhat it is: CVE-2026-30913 is a medium-severity cross-site scripting vulnerability in flarum nicknames, published on 9 Mar 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-30913 exists.\n\nAffected packages and fixed versions:\n- flarum/nicknames (Packagist): affected all versions; fixed in 1.8.3\n- flarum/nicknames (Packagist): affected all versions; fixed in 1.8.3\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-30913/ (Markdown: https://insights.sbomify.com/CVE-2026-30913/index.md)","id":"CVE-2026-30913","markdown":"https://insights.sbomify.com/CVE-2026-30913/index.md","name":"CVE-2026-30913","record":{"aliases":["GHSA-3c4m-j3g4-hh25"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Flarum forum plugin","requires_auth":"low_privilege","summary":"Attackers can inject malicious links into notification emails via nicknames, misleading users to visit attacker-controlled domains.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Flarum is open-source forum software. When the flarum/nicknames extension is enabled, a registered user can set their nickname to a string that email clients interpret as a hyperlink. The nickname is inserted verbatim into plain-text notification emails, and recipients may be misled into visiting attacker-controlled domains.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"flarum/nickname: Display name injection in notification emails (autolink \u0026 markdown)","id":"CVE-2026-30913","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"SFTPGo has a Path Traversal and Permission Bypass via Path Normalization Discrepancy","id":"CVE-2026-30914"},"packages":[{"ecosystem":"Packagist","fixed":["1.8.3"],"introduced":["0"],"last_affected":[],"package":"flarum/nicknames","purl":null,"source":"GHSA-3c4m-j3g4-hh25"},{"ecosystem":"Packagist","fixed":["1.8.3"],"introduced":["0"],"last_affected":[],"package":"flarum/nicknames","purl":"pkg:composer/flarum/nicknames","source":"GHSA-3c4m-j3g4-hh25"}],"prev":{"headline":"Apache Airflow: Exposing stack trace in case of constraint error","id":"CVE-2026-30912"},"products":["nicknames"],"published":"2026-03-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-03-10","vendors":["flarum"]},"summary":"Attackers can inject malicious links into notification emails via nicknames, misleading users to visit attacker-controlled domains.","url":"https://insights.sbomify.com/CVE-2026-30913/"}