{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-31113 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-31113 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-31113 is a medium-severity cross-site scripting vulnerability in thinkst canarytokens, published on 1 Jul 2022. 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-2022-31113 and fix it if it is affected.\n\nWhat it is: CVE-2022-31113 is a medium-severity cross-site scripting vulnerability in thinkst canarytokens, published on 1 Jul 2022. 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-2022-31113 in the wild and no public exploit code.\n\nAffected product: thinkst canarytokens. 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-2022-31113/ (Markdown: https://insights.sbomify.com/CVE-2022-31113/index.md)","id":"CVE-2022-31113","markdown":"https://insights.sbomify.com/CVE-2022-31113/index.md","name":"CVE-2022-31113","record":{"aliases":["GHSA-5675-3424-hpqr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Canarytokens web tool","requires_auth":"none","summary":"Attackers can execute JavaScript in the history page of triggered Canarytokens, potentially viewing or modifying token data and exposing creator information.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"canarytokens","vendor":"thinkst"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Canarytokens is an open source tool which helps track activity and actions on your network. A Cross-Site Scripting vulnerability was identified in the history page of triggered Canarytokens. This permits an attacker who recognised an HTTP-based Canarytoken (a URL) to execute Javascript in the Canarytoken's history page (domain: canarytokens.org) when the history page is later visited by the Canarytoken's creator. This vulnerability could be used to disable or delete the affected Canarytoken, or view its activation history. It might also be used as a stepping stone towards revealing more information about the Canarytoken's creator to the attacker. For example, an attacker could recover the email address tied to the Canarytoken, or place Javascript on the history page that redirect the creator towards an attacker-controlled Canarytoken to show the creator's network location. An attacker could only act on the discovered Canarytoken. This issue did not expose other Canarytokens or other Canarytoken creators. The issue has been patched on Canarytokens.org and in the latest release. No signs of successful exploitation of this vulnerability have been found. Users are advised to upgrade. There are no known workarounds for this issue.","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":"Cross-Site Scripting in Canarytoken history","id":"CVE-2022-31113","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"backpack/crud Vulnerable to Cross-site Scripting","id":"CVE-2022-31114"},"packages":[],"prev":{"headline":"Protected fields exposed via LiveQuery in parse-server","id":"CVE-2022-31112"},"products":["canarytokens"],"published":"2022-07-01","related":[{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2019-9768","kev_date_added":null,"published":"2019-03-14"},{"cvss_score":6.5,"headline":"CSV Injection in exported history CSV files","id":"CVE-2024-28111","kev_date_added":null,"published":"2024-03-06"},{"cvss_score":6.3,"headline":"Cross-Site Scripting in Canarytoken history","id":"CVE-2023-22475","kev_date_added":null,"published":"2023-01-06"}],"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-04-23","vendors":["thinkst"]},"summary":"Attackers can execute JavaScript in the history page of triggered Canarytokens, potentially viewing or modifying token data and exposing creator information.","url":"https://insights.sbomify.com/CVE-2022-31113/"}