{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-34413 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-34413 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-34413 is a high-severity vulnerability in DigitalPA S.r.l. Legality WHISTLEBLOWING, published on 9 Dec 2025. 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-2025-34413 and fix it if it is affected.\n\nWhat it is: CVE-2025-34413 is a high-severity vulnerability in DigitalPA S.r.l. Legality WHISTLEBLOWING, published on 9 Dec 2025. 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-2025-34413 in the wild and no public exploit code.\n\nAffected product: DigitalPA S.r.l. Legality WHISTLEBLOWING. 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-2025-34413/ (Markdown: https://insights.sbomify.com/CVE-2025-34413/index.md)","id":"CVE-2025-34413","markdown":"https://insights.sbomify.com/CVE-2025-34413/index.md","name":"CVE-2025-34413","record":{"aliases":["GHSA-r4xg-7r26-r275"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Legality WHISTLEBLOWING","requires_auth":"none","summary":"The application fails to emit critical HTTP security headers by default, weakening browser defenses against client-side attacks like XSS and clickjacking.","user_interaction":"required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"Legality WHISTLEBLOWING by DigitalPA contains a protection mechanism failure in which critical HTTP security headers are not emitted by default. Affected deployments omit Content-Security-Policy, Referrer-Policy, Permissions-Policy, Cross-Origin-Embedder-Policy, Cross-Origin-Opener-Policy, and Cross-Origin-Resource-Policy (with CSP delivered via HTML meta elements being inadequate). The absence of these headers weakens browser-side defenses and increases exposure to client-side attacks such as cross-site scripting, clickjacking, referer leakage, and cross-origin data disclosure.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Legality WHISTLEBLOWING Missing Critical HTTP Security Headers","id":"CVE-2025-34413","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Entrust Instant Financial Issuance (IFI) Legacy Remoting Service .NET Remoting RCE","id":"CVE-2025-34414"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it identified a vulnerability in a SaaS product that does","id":"CVE-2025-34412"},"products":["Legality WHISTLEBLOWING"],"published":"2025-12-09","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-09","vendors":["DigitalPA S.r.l."]},"summary":"The application fails to emit critical HTTP security headers by default, weakening browser defenses against client-side attacks like XSS and clickjacking.","url":"https://insights.sbomify.com/CVE-2025-34413/"}