{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41139 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41139 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41139 is a high-severity cross-site scripting vulnerability in anuko timetracker, published on 13 Oct 2021. 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-2021-41139 and fix it if it is affected.\n\nWhat it is: CVE-2021-41139 is a high-severity cross-site scripting vulnerability in anuko timetracker, published on 13 Oct 2021. 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-2021-41139 in the wild and no public exploit code.\n\nAffected product: anuko timetracker. 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-2021-41139/ (Markdown: https://insights.sbomify.com/CVE-2021-41139/index.md)","id":"CVE-2021-41139","markdown":"https://insights.sbomify.com/CVE-2021-41139/index.md","name":"CVE-2021-41139","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Time tracking application","requires_auth":"none","summary":"Reflected XSS in Anuko Time Tracker allows attackers to execute malicious JavaScript in a logged-in user's browser via a crafted link.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"time_tracker","vendor":"anuko"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Anuko Time Tracker is an open source, web-based time tracking application written in PHP. When a logged on user selects a date in Time Tracker, it is being passed on via the date parameter in URI. Because of not checking this parameter for sanity in versions prior to 1.19.30.5600, it was possible to craft the URI with malicious JavaScript, use social engineering to convince logged on user to click on such link, and have the attacker-supplied JavaScript to be executed in user's browser. This issue is patched in version 1.19.30.5600. As a workaround, one may introduce `ttValidDbDateFormatDate` function as in the latest version and add a call to it within the access checks block in time.php.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Reflected XSS vulnerability in time.php","id":"CVE-2021-41139","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Reactions leak for secure category topics and private messages","id":"CVE-2021-41140"},"packages":[],"prev":{"headline":"Validity check for signed Frontier-specific extrinsic not called in block execution","id":"CVE-2021-41138"},"products":["timetracker"],"published":"2021-10-13","related":[{"cvss_score":9.8,"headline":"Business logic in n/a","id":"CVE-2020-27422","kev_date_added":null,"published":"2020-11-16"},{"cvss_score":8.8,"headline":"Time Tracker has Blind SQL Injection Vulnerability in Reports","id":"CVE-2023-32306","kev_date_added":null,"published":"2023-05-12"},{"cvss_score":8.7,"headline":"CSV injection in Anuko Time Tracker","id":"CVE-2020-15255","kev_date_added":null,"published":"2020-10-16"},{"cvss_score":8.2,"headline":"SQL Injection Vulnerability in anuko timetracker","id":"CVE-2023-32308","kev_date_added":null,"published":"2023-05-15"},{"cvss_score":8.1,"headline":"SQL injection vulnerability in anuko timetracker","id":"CVE-2021-43851","kev_date_added":null,"published":"2021-12-21"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2020-27423","kev_date_added":null,"published":"2020-11-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["anuko"]},"summary":"Reflected XSS in Anuko Time Tracker allows attackers to execute malicious JavaScript in a logged-in user's browser via a crafted link.","url":"https://insights.sbomify.com/CVE-2021-41139/"}