CVE-2026-55562: Cronicle: Stored XSS in admin Activity Log via account full_name field
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Cronicle is a multi-server task scheduler and runner, with a web based front-end UI. Prior to 0.9.119, the administrator Activity Log in htdocs/js/pages/admin/Activity.js concatenates the attacker-controlled item.user.full_name value into HTML without applying encode_entities and inserts the result through this.div.html. The bundled pixl-server-user input filter can be bypassed by a tag containing a line break because its regular expression does not match newlines. An authenticated non-administrator can update the attacker’s own name through /api/user/update using a valid session and current password; when free_accounts is enabled, an anonymous attacker can instead plant the name during self-registration. The stored name executes script in an administrator’s session when the Activity Log is opened, enabling administrator takeover and subsequent command execution through privileged Cronicle features. This issue is fixed in version 0.9.119.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-13).
Weakness: CWE-79: Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’)
How it can be exploited
Exploitable over the network with low attack complexity needing low privileges and a user must take an action. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Also known as: EUVD-2026-98908
VEDAS cluster: VEDAS:DOLPHINCALL
Exploit Observer links 3 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (3)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-55562.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-55562.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-55562.rules
Vulnerability databases and vendor advisories (2)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-98908
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-55562
2 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.005
low predicted chance of attack - VEDAS
- 0.985
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| jhuckaby Cronicle | version < 0.9.119 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-55562 Cronicle - Stored Cross-Site Scripting. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-55562 Cronicle - Stored Cross-Site Scripting"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/user/update"; nocase; fast_pattern; http.request_body; content:"full_name"; nocase; pcre:"/\x22full_name\x22\s*:\s*\x22[^\x22]*<[a-z]+[^>]*(?:onerror|onload|onmouseover|src\s*=|script)/i"; classtype:web-application-attack; reference:cve,CVE-2026-55562; reference:url,https://www.exploit.observer/?keyword=CVE-2026-55562&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=cronicle&match=exact; sid:1084203; rev:1;)
CVE-2026-55562.rules on GitHub
References
Other references
- https://github.com/jhuckaby/Cronicle/security/advisories/GHSA-vh39-3pcm-2j63 (x_refsource_CONFIRM)
- https://github.com/jhuckaby/Cronicle/commit/8b60eb5b041614ab661df50e58e612f5e42a7d30 (x_refsource_MISC)
- https://github.com/jhuckaby/Cronicle/releases/tag/v0.9.119 (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.