{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35460 exists.","fix":"No fix has been published for CVE-2026-35460 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-35460 is a medium-severity cross-site scripting vulnerability in papra-hq papra, published on 7 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-35460 and fix it if it is affected.\n\nWhat it is: CVE-2026-35460 is a medium-severity cross-site scripting vulnerability in papra-hq papra, published on 7 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35460 exists.\n\nAffected product: papra-hq papra. 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-35460/ (Markdown: https://insights.sbomify.com/CVE-2026-35460/index.md)","id":"CVE-2026-35460","markdown":"https://insights.sbomify.com/CVE-2026-35460/index.md","name":"CVE-2026-35460","record":{"aliases":["GHSA-6f8x-2rc9-vgh4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Document management platform","requires_auth":"low_privilege","summary":"Attackers can inject HTML into transactional emails via unescaped display names, enabling convincing phishing attacks from legitimate domains.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"papra","vendor":"papra"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-80","name":"Improper Neutralization of Script-Related HTML Tags in a Web Page"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Papra is a minimalistic document management and archiving platform. Prior to 26.4.0, transactional email templates in Papra interpolate user.name directly into HTML without escaping or sanitization. An attacker who registers with a display name containing HTML tags will have those tags injected into the verification and password reset email bodies. Since emails are sent from the legitimate domain (e.g: auth@mail.papra.app), this enables convincing phishing attacks that appear to originate from official Papra notifications. This vulnerability is fixed in 26.4.0.","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":"Papra has an HTML Injection in Transactional Emails via Unescaped User Display Name","id":"CVE-2026-35460","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Papra has a Blind Server-Side Request Forgery (SSRF) via Webhook URL","id":"CVE-2026-35461"},"packages":[],"prev":{"headline":"pyLoad has SSRF fix bypass via HTTP redirect","id":"CVE-2026-35459"},"products":["papra"],"published":"2026-04-07","related":[{"cvss_score":5,"headline":"Papra has a Blind Server-Side Request Forgery (SSRF) via Webhook URL","id":"CVE-2026-35461","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":4.3,"headline":"Papra Does Not Reject Expired API Keys","id":"CVE-2026-35462","kev_date_added":null,"published":"2026-04-07"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["papra-hq"]},"summary":"Attackers can inject HTML into transactional emails via unescaped display names, enabling convincing phishing attacks from legitimate domains.","url":"https://insights.sbomify.com/CVE-2026-35460/"}