{"answers":{"affected":"2 open source packages ship an affected version, including kimai/kimai.","exploited":"There is no known exploitation of CVE-2026-52823 in the wild and no public exploit code.","fix":"Upgrade kimai/kimai to 2.58.0 or later.","what":"CVE-2026-52823 is a medium-severity vulnerability in kimai, published on 15 Sep 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-52823 and fix it if it is affected.\n\nWhat it is: CVE-2026-52823 is a medium-severity vulnerability in kimai, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-52823 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kimai/kimai (Packagist): affected all versions; fixed in 2.58.0\n- kimai/kimai (Packagist): affected all versions; fixed in 2.58.0\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-52823/ (Markdown: https://insights.sbomify.com/CVE-2026-52823/index.md)","id":"CVE-2026-52823","markdown":"https://insights.sbomify.com/CVE-2026-52823/index.md","name":"CVE-2026-52823","record":{"aliases":["GHSA-r8vr-m544-qh4h"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Kimai time tracking","requires_auth":"low_privilege","summary":"Attackers can force logged-in users to stop or restart timesheets via GET requests, corrupting time records and billing data.","user_interaction":"not_required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Kimai is an open-source time tracking application. Prior to 2.58.0, TimesheetController exposes GET /api/timesheets/{id}/stop and GET /api/timesheets/{id}/restart, which reuse an authenticated browser session and perform state-changing operations through GET requests without a request-forgery defense. A remote attacker can cause a logged-in user to request either route from attacker-controlled content, stopping a running timesheet or restarting a historical entry to create and start a new timesheet without the user's consent. The unauthorized changes can corrupt time records, billing, reports, approvals, and audits. This issue is fixed in version 2.58.0.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Kimai: Login CSRF in Kimai Timesheet Stop and Restart API Endpoints Allows Unauthorized State Changes","id":"CVE-2026-52823","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"Kimai: Default APP_SECRET in Docker Image Enables Cookie Forgery and Account Takeover","id":"CVE-2026-52824"},"packages":[{"ecosystem":"Packagist","fixed":["2.58.0"],"introduced":["0"],"last_affected":[],"package":"kimai/kimai","purl":null,"source":"GHSA-r8vr-m544-qh4h"},{"ecosystem":"Packagist","fixed":["2.58.0"],"introduced":["0"],"last_affected":[],"package":"kimai/kimai","purl":"pkg:composer/kimai/kimai","source":"GHSA-r8vr-m544-qh4h"}],"prev":{"headline":"Improper Authorization in Kimai Timesheet Restart and Duplicate Allows New Timesheets After Project Access Revocation","id":"CVE-2026-52822"},"products":["kimai"],"published":"2026-09-15","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-15","vendors":["kimai"]},"summary":"Attackers can force logged-in users to stop or restart timesheets via GET requests, corrupting time records and billing data.","url":"https://insights.sbomify.com/CVE-2026-52823/"}