CVE-2026-39400
Stored Cross-Site Scripting in Cronicle Job Output Fields
Publication date: 2026-04-07
Last updated on: 2026-04-15
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| cronicle | cronicle | to 0.9.111 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Cronicle, a multi-server task scheduler with a web-based UI. Before version 0.9.111, a non-admin user who has the privileges to create and run events can inject arbitrary JavaScript code through certain job output fields such as html.content, html.title, table.header, table.rows, and table.caption.
The server stores this injected data without sanitizing it, and the client renders it using innerHTML on the Job Details page, which leads to the execution of the malicious JavaScript.
This vulnerability was fixed in version 0.9.111.
How can this vulnerability impact me? :
The vulnerability allows a non-admin user with specific privileges to execute arbitrary JavaScript in the context of the web application.
This can lead to cross-site scripting (XSS) attacks, which may result in unauthorized actions, data theft, session hijacking, or other malicious activities performed on behalf of the victim user.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade Cronicle to version 0.9.111 or later, where the issue has been fixed.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows a non-admin user with certain privileges to inject arbitrary JavaScript into job output fields, which is then stored without sanitization and rendered on the client side. This could potentially lead to unauthorized data access or manipulation.
Such unauthorized script injection and potential data exposure could impact compliance with standards like GDPR and HIPAA, which require protection of personal and sensitive data against unauthorized access and ensure data integrity.
However, the provided information does not explicitly state the direct impact on compliance with these regulations.