Chronoframe
Monthly
Unauthenticated configuration takeover of ChronoFrame 1.0.0 and earlier lets any attacker who can reach the HTTP service POST to the setup-wizard API and repoint instance storage to an attacker-controlled S3 or OpenList backend while overwriting site and map settings. The flaw covers every release through 1.0.0 (CPE cpe:2.3:a:hoshinosuzumi:chronoframe:*:*:*:*:*:*:*:*) and remains exploitable on instances where initial setup is already complete, because the /api/wizard/ handlers enforce neither authentication nor a setup-complete check. No public exploit identified at time of analysis and no CISA KEV entry, though a public technical writeup describes the attack path; the independent assessment (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L) rates this high priority for any network-exposed deployment.
Unauthenticated configuration takeover of ChronoFrame 1.0.0 and earlier lets any attacker who can reach the HTTP service POST to the setup-wizard API and repoint instance storage to an attacker-controlled S3 or OpenList backend while overwriting site and map settings. The flaw covers every release through 1.0.0 (CPE cpe:2.3:a:hoshinosuzumi:chronoframe:*:*:*:*:*:*:*:*) and remains exploitable on instances where initial setup is already complete, because the /api/wizard/ handlers enforce neither authentication nor a setup-complete check. No public exploit identified at time of analysis and no CISA KEV entry, though a public technical writeup describes the attack path; the independent assessment (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L) rates this high priority for any network-exposed deployment.