A security vulnerability was identified in Obsidian Scheduler's REST API 5.0.0 thru 6.3.0. If an account is locked out due to not enrolling in MFA (e.g. after the 7-day enforcement window), the REST API still allows the use of Basic Authentication to authenticate and perform administrative actions. In particular, the default admin account was found to be locked out via the web interface but still usable through the REST API. This allowed creation of a new privileged user, bypassing MFA protections. This undermines the intended security posture of MFA enforcement.
History

Tue, 30 Sep 2025 09:00:00 +0000

Type Values Removed Values Added
First Time appeared Obsidian Scheduler
Obsidian Scheduler rest Api
Vendors & Products Obsidian Scheduler
Obsidian Scheduler rest Api

Mon, 29 Sep 2025 14:30:00 +0000

Type Values Removed Values Added
Description A security vulnerability was identified in Obsidian Scheduler's REST API 5.0.0 thru 6.3.0. If an account is locked out due to not enrolling in MFA (e.g. after the 7-day enforcement window), the REST API still allows the use of Basic Authentication to authenticate and perform administrative actions. In particular, the default admin account was found to be locked out via the web interface but still usable through the REST API. This allowed creation of a new privileged user, bypassing MFA protections. This undermines the intended security posture of MFA enforcement.
References

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2025-09-29T14:11:16.624Z

Reserved: 2025-08-17T00:00:00.000Z

Link: CVE-2025-56449

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2025-09-29T15:16:08.653

Modified: 2025-09-29T19:34:10.030

Link: CVE-2025-56449

cve-icon Redhat

No data.