{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54199 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54199 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54199 is a medium-severity vulnerability in Tobit Laboratories AG TeamDavid, published on 7 Aug 2026. 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-2026-54199 and fix it if it is affected.\n\nWhat it is: CVE-2026-54199 is a medium-severity vulnerability in Tobit Laboratories AG TeamDavid, published on 7 Aug 2026. 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-2026-54199 in the wild and no public exploit code.\n\nAffected product: Tobit Laboratories AG TeamDavid. 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-54199/ (Markdown: https://insights.sbomify.com/CVE-2026-54199/index.md)","id":"CVE-2026-54199","markdown":"https://insights.sbomify.com/CVE-2026-54199/index.md","name":"CVE-2026-54199","record":{"aliases":["GHSA-pfmg-m2fv-v732"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["security_bypass","other"],"network_reachable":"yes","non_default_config":false,"product_category":"TeamDavid Webbox","requires_auth":"none","summary":"Attackers can inject HTTP headers via the request body in the link storing feature, potentially manipulating redirect responses.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NCSC.ch","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Tobit Laboratories AG TeamDavid's Webbox  is vulnerable to HTTP header injection through the \nrequest body in the application's link storing functionality \n(//ServerClient_celink.htm), which is appended to the redirect target in\n the 302 HTTP response. If a line feed is added, this will also be added\n to the redirect link, resulting in the ability to control the response \nheaders. This issue affects TeamDavid before Rollout 528.\n\nStarting with Rollout 528 (June 30, 2026), the affected functionality is disabled by default and the vulnerabilities are therefore no longer exposed through this functionality.","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":"TeamDavid: Header Injection through request body in link storing functionality","id":"CVE-2026-54199","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"TeamDavid: Local File Inclusion via the form field 'scjob'","id":"CVE-2026-54200"},"packages":[],"prev":{"headline":"WordPress Media LIbrary Assistant plugin \u003c= 3.35 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2026-54198"},"products":["TeamDavid"],"published":"2026-08-07","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":"2026-09-07","vendors":["Tobit Laboratories AG"]},"summary":"Attackers can inject HTTP headers via the request body in the link storing feature, potentially manipulating redirect responses.","url":"https://insights.sbomify.com/CVE-2026-54199/"}