CVE-2026-55562: Cross-Site Scripting Flaw in jhuckaby Cronicle Scores 9 on CVSS
A newly published critical vulnerability in jhuckaby Cronicle carries a CVSS score of 9. Here is what is affected and how to respond.
Key points
- CVE-2026-55562 affects jhuckaby Cronicle.
- CVSS 9 (Critical).
- No exploitation confirmed yet.
A critical cross-site scripting tracked as CVE-2026-55562 has been published in the National Vulnerability Database for jhuckaby Cronicle, with a CVSS base score of 9.
At a glance
- CVE
- CVE-2026-55562
- Product
- jhuckaby Cronicle
- CVSS
- 9 Critical
- Weakness
- cross-site scripting
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: 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 Cronic
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Jhuckaby | Cronicle | < 0.9.119 |
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H.
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-55562
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-55562?
CVE-2026-55562 is a cross-site scripting vulnerability in jhuckaby Cronicle.
How severe is CVE-2026-55562?
It has a CVSS score of 9 Critical.
Is CVE-2026-55562 being exploited?
There is no public confirmation of exploitation at the time of publication.
