{"answers":{"affected":"2 open source packages ship an affected version, including uptime-kuma. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-44400 exists.","fix":"Upgrade uptime-kuma to 1.23.3 or later.","what":"CVE-2023-44400 is a medium-severity vulnerability in louislam uptime-kuma, published on 9 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-44400 and fix it if it is affected.\n\nWhat it is: CVE-2023-44400 is a medium-severity vulnerability in louislam uptime-kuma, published on 9 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-44400 exists.\n\nAffected packages and fixed versions:\n- uptime-kuma (npm): affected all versions; fixed in 1.23.3\n- uptime-kuma (npm): affected all versions; fixed in 1.23.3\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-2023-44400/ (Markdown: https://insights.sbomify.com/CVE-2023-44400/index.md)","id":"CVE-2023-44400","markdown":"https://insights.sbomify.com/CVE-2023-44400/index.md","name":"CVE-2023-44400","record":{"aliases":["GHSA-g9v2-wqcj-j99g"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Uptime Kuma monitoring tool","requires_auth":"high_privilege","summary":"Attackers with device access can maintain persistent account access in Uptime Kuma due to missing session token verification after password changes or inactivity.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"uptime_kuma","vendor":"uptime.kuma"}],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-384","name":"Session Fixation"}],"description":"Uptime Kuma is a self-hosted monitoring tool. Prior to version 1.23.3, attackers with access to a user's device can gain persistent account access. This is caused by missing verification of Session Tokens after password changes and/or elapsed inactivity periods. Version 1.23.3 has a patch for the issue.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Uptime Kuma has Persistentent User Sessions","id":"CVE-2023-44400","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":2,"n_references":3,"next":{"headline":"Silverstripe GraqhQL's view permissions are bypassed for paginated lists of ORM data","id":"CVE-2023-44401"},"packages":[{"ecosystem":"npm","fixed":["1.23.3"],"introduced":["0"],"last_affected":[],"package":"uptime-kuma","purl":null,"source":"GHSA-g9v2-wqcj-j99g"},{"ecosystem":"npm","fixed":["1.23.3"],"introduced":["0"],"last_affected":[],"package":"uptime-kuma","purl":"pkg:npm/uptime-kuma","source":"GHSA-g9v2-wqcj-j99g"}],"prev":{"headline":"ZITADEL's password reset does not respect the \"Ignoring unknown usernames\" setting","id":"CVE-2023-44399"},"products":["uptime-kuma"],"published":"2023-10-09","related":[{"cvss_score":6.5,"headline":"Uptime Kuma: SSTI in Notification Templates Allows Arbitrary File Read (Incomplete Fix for GHSA-vffh-c9pq-4crh)","id":"CVE-2026-33130","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":6.3,"headline":"Attribute Injection leading to XSS(Cross-Site-Scripting) in uptime-kuma","id":"CVE-2023-49276","kev_date_added":null,"published":"2023-12-01"},{"cvss_score":5.3,"headline":"Uptime Kuma is Missing Authorization Checks on Ping Badge Endpoint, Leaks Ping times of monitors without needing to be on a status page","id":"CVE-2026-32230","kev_date_added":null,"published":"2026-03-12"}],"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":"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":"total"},"state":"PUBLISHED","updated":"2024-09-18","vendors":["louislam"]},"summary":"Attackers with device access can maintain persistent account access in Uptime Kuma due to missing session token verification after password changes or inactivity.","url":"https://insights.sbomify.com/CVE-2023-44400/"}