{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-25810 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-25810 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-25810 is a medium-severity cross-site scripting vulnerability in louislam uptime-kuma, published on 21 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-25810 and fix it if it is affected.\n\nWhat it is: CVE-2023-25810 is a medium-severity cross-site scripting vulnerability in louislam uptime-kuma, published on 21 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-25810 in the wild and no public exploit code.\n\nAffected product: louislam uptime-kuma. 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-2023-25810/ (Markdown: https://insights.sbomify.com/CVE-2023-25810/index.md)","id":"CVE-2023-25810","markdown":"https://insights.sbomify.com/CVE-2023-25810/index.md","name":"CVE-2023-25810","record":{"aliases":["GHSA-wh8j-xr66-f296"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Uptime Kuma monitoring tool","requires_auth":"low_privilege","summary":"Attackers can inject persistent scripts into the status page description, potentially executing code or hijacking user sessions in Uptime Kuma.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"uptime-kuma","vendor":"uptime-kuma_project"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Uptime Kuma is a self-hosted monitoring tool. In versions prior to 1.20.0 the Uptime Kuma status page allows a persistent XSS attack. Users are advised to upgrade. There are no known workarounds for this vulnerability.","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":"Persistent Cross site scripting (XSS) through description in status page in Uptime Kuma","id":"CVE-2023-25810","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Persistent Cross site scripting (XSS) in Uptime Kuma","id":"CVE-2023-25811"},"packages":[],"prev":{"headline":"rootless: `/sys/fs/cgroup` is writable when cgroupns isn't unshared in runc","id":"CVE-2023-25809"},"products":["uptime-kuma"],"published":"2023-02-21","related":[{"cvss_score":8.8,"headline":"Uptime Kuma vulnerable to authenticated remote code execution via malicious plugin installation","id":"CVE-2023-36821","kev_date_added":null,"published":"2023-07-05"},{"cvss_score":6.5,"headline":"Uptime Kuma authenticated path traversal via plugin repository name may lead to unavailability or data loss","id":"CVE-2023-36822","kev_date_added":null,"published":"2023-07-05"},{"cvss_score":6.3,"headline":"Persistent Cross site scripting (XSS) in Uptime Kuma","id":"CVE-2023-25811","kev_date_added":null,"published":"2023-02-21"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["louislam"]},"summary":"Attackers can inject persistent scripts into the status page description, potentially executing code or hijacking user sessions in Uptime Kuma.","url":"https://insights.sbomify.com/CVE-2023-25810/"}