LiveActive security incident?Get immediate response
CVE Record

CVE-2022-31113: Cross-Site Scripting in Canarytoken history

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.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-31113 is a stored cross-site scripting flaw in the Canarytokens trigger history page. If an attacker discovered an HTTP Canarytoken URL, they could place JavaScript that runs when the token creator later views that token’s history. The known impact is limited to the discovered token, not all tokens or users.

Executive priority

Treat as a bounded but real security hygiene issue. It is not currently known to be exploited, but vulnerable self-hosted deployments could let an attacker tamper with or learn about a discovered Canarytoken.

Technical view

The flaw is CWE-79 in Thinkst Canarytokens history rendering before commit dc378957bc28a6f3b5a8d7217b0605d81111f090. The CVSS 3.1 score is 6.3. Exploitation requires network access, no authentication, and user interaction by the token creator visiting the history page.

Likely exposure

Hosted canarytokens.org was patched. Remaining concern is self-hosted Canarytokens instances or source deployments built from commits before the referenced fix, especially where HTTP-based tokens are used and creators review trigger history.

Exploitation context

Sources state no signs of successful exploitation were found, and this CVE is not in KEV. An attacker would need to recognize a specific HTTP Canarytoken and wait for its creator to view the affected history page.

Researcher notes

Impact is constrained by source evidence: only the discovered Canarytoken is affected. Possible outcomes include viewing activation history, disabling or deleting that token, or learning limited creator information. Do not broaden exposure beyond the advisory.

Mitigation direction

  • Upgrade Canarytokens to a release containing commit dc378957bc28a6f3b5a8d7217b0605d81111f090.
  • Confirm canarytokens.org users rely on the patched hosted service.
  • For self-hosted deployments, check vendor advisory before delaying remediation.
  • Assume there are no known workarounds unless vendor guidance changes.

Validation and detection

  • Inventory any self-hosted Thinkst Canarytokens deployments.
  • Verify the deployed code includes commit dc378957bc28a6f3b5a8d7217b0605d81111f090 or later.
  • Identify whether HTTP-based Canarytokens are in use.
  • Review available audit data for unexpected token disablement, deletion, or history access.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-31113 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L2.83.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.3Medium
CVSS 3.1 vector shape for CVE-2022-31113Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
thinkstcanarytokensCommits prior to dc378957bc28a6f3b5a8d7217b0605d81111f090Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.