{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21695 exists.","fix":"No fix has been published for CVE-2026-21695 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-21695 is a medium-severity vulnerability in kromitgmbh titra, published on 7 Jan 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-21695 and fix it if it is affected.\n\nWhat it is: CVE-2026-21695 is a medium-severity vulnerability in kromitgmbh titra, published on 7 Jan 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-21695 exists.\n\nAffected product: kromitgmbh titra. 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-21695/ (Markdown: https://insights.sbomify.com/CVE-2026-21695/index.md)","id":"CVE-2026-21695","markdown":"https://insights.sbomify.com/CVE-2026-21695/index.md","name":"CVE-2026-21695","record":{"aliases":["GHSA-gc65-vr47-jppq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Time tracking software","requires_auth":"low_privilege","summary":"Authenticated attackers can modify protected time entry fields like hours and state by injecting arbitrary keys into the customfields parameter.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"titra","vendor":"kromit"}],"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-915","name":"Improperly Controlled Modification of Dynamically-Determined Object Attributes"}],"description":"Titra is open source project time tracking software. In versions 0.99.49 and below, an API has a Mass Assignment vulnerability which allows authenticated users to inject arbitrary fields into time entries, bypassing business logic controls via the customfields parameter. The affected endpoint uses the JavaScript spread operator (...customfields) to merge user-controlled input directly into the database document. While customfields is validated as an Object type, there is no validation of which keys are permitted inside that object. This allows attackers to overwrite protected fields such as userId, hours, and state. The issue is fixed in version 0.99.50.","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":"Titra API Contains Mass Assignment Vulnerability","id":"CVE-2026-21695","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Endless reprocessing/reupload of activity log data due to SQLite max parameters limit not being considered","id":"CVE-2026-21696"},"packages":[],"prev":{"headline":"Titra APIs have Improper Access Control","id":"CVE-2026-21694"},"products":["titra"],"published":"2026-01-07","related":[{"cvss_score":9.8,"headline":"Improper Authorization in kromitgmbh/titra","id":"CVE-2022-2595","kev_date_added":null,"published":"2022-08-01"},{"cvss_score":9.1,"headline":"Titra has Remote Code Execution in Admin Functionality","id":"CVE-2025-69288","kev_date_added":null,"published":"2025-12-31"},{"cvss_score":8.2,"headline":"Cross-site Scripting (XSS) - Stored in kromitgmbh/titra","id":"CVE-2022-2026","kev_date_added":null,"published":"2022-06-08"},{"cvss_score":8.2,"headline":"Cross-site Scripting (XSS) - Generic in kromitgmbh/titra","id":"CVE-2022-2028","kev_date_added":null,"published":"2022-06-08"},{"cvss_score":8.2,"headline":"Cross-site Scripting (XSS) - DOM in kromitgmbh/titra","id":"CVE-2022-2029","kev_date_added":null,"published":"2022-06-08"},{"cvss_score":8,"headline":"Improper Neutralization of Formula Elements in a CSV File in kromitgmbh/titra","id":"CVE-2022-2027","kev_date_added":null,"published":"2022-06-08"},{"cvss_score":7.1,"headline":"Weak Password Requirements in kromitgmbh/titra","id":"CVE-2022-2098","kev_date_added":null,"published":"2022-06-16"}],"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-01-08","vendors":["kromitgmbh"]},"summary":"Authenticated attackers can modify protected time entry fields like hours and state by injecting arbitrary keys into the customfields parameter.","url":"https://insights.sbomify.com/CVE-2026-21695/"}