{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-39400 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-39400 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-39400 is a medium-severity cross-site scripting vulnerability in jhuckaby Cronicle, published on 7 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-39400 and fix it if it is affected.\n\nWhat it is: CVE-2026-39400 is a medium-severity cross-site scripting vulnerability in jhuckaby Cronicle, published on 7 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-39400 in the wild and no public exploit code.\n\nAffected product: jhuckaby Cronicle. 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-2026-39400/ (Markdown: https://insights.sbomify.com/CVE-2026-39400/index.md)","id":"CVE-2026-39400","markdown":"https://insights.sbomify.com/CVE-2026-39400/index.md","name":"CVE-2026-39400","record":{"aliases":["GHSA-36q6-pwxv-j545"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Cronicle task scheduler","requires_auth":"low_privilege","summary":"A non-admin user can inject arbitrary JavaScript via job output fields, leading to stored XSS and potential account takeover in Cronicle.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cronicle","vendor":"cronicle"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Cronicle is a multi-server task scheduler and runner, with a web based front-end UI. Prior to 0.9.111, a non-admin user with create_events and run_events privileges can inject arbitrary JavaScript through job output fields (html.content, html.title, table.header, table.rows, table.caption). The server stores this data without sanitization, and the client renders it via innerHTML on the Job Details page. This vulnerability is fixed in 0.9.111.","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":"Stored XSS via Job HTML/Table Output in Cronicle","id":"CVE-2026-39400","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege Escalation via update_event Job Output in Cronicle","id":"CVE-2026-39401"},"packages":[],"prev":{"headline":"NuGet Gallery: Arbitrary Blob Overwrite via Nuspec Confusion and URI Fragment Truncation","id":"CVE-2026-39399"},"products":["Cronicle"],"published":"2026-04-07","related":[{"cvss_score":5.3,"headline":"Privilege Escalation via update_event Job Output in Cronicle","id":"CVE-2026-39401","kev_date_added":null,"published":"2026-04-07"}],"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":"2026-04-15","vendors":["jhuckaby"]},"summary":"A non-admin user can inject arbitrary JavaScript via job output fields, leading to stored XSS and potential account takeover in Cronicle.","url":"https://insights.sbomify.com/CVE-2026-39400/"}