Obsidian Scheduler up to 6.3.0 REST API improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Obsidian Scheduler up to 6.3.0. Impacted is an unknown function of the component REST API. The manipulation leads to improper authentication. This vulnerability is listed as CVE-2025-56449. There is no available exploit.
Details
A vulnerability, which was classified as critical, has been found in Obsidian Scheduler up to 6.3.0. This issue affects an unknown functionality of the component REST API. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at blog.gregscharf.com. The identification of this vulnerability is CVE-2025-56449 since 08/17/2025. The exploitation is known to be easy. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at EUVD (EUVD-2025-31578) and CERT Bund (WID-SEC-2025-2158). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- Obsidian Obsidian
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/17/2025 CVE reserved09/29/2025 Advisory disclosed
09/29/2025 VulDB entry created
10/29/2025 VulDB entry last update
Sources
Advisory: blog.gregscharf.comStatus: Not defined
CVE: CVE-2025-56449 (🔒)
GCVE (CVE): GCVE-0-2025-56449
GCVE (VulDB): GCVE-100-326243
EUVD: 🔒
CERT Bund: WID-SEC-2025-2158 - Obsidian: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen
Entry
Created: 09/29/2025 17:30Updated: 10/29/2025 05:25
Changes: 09/29/2025 17:30 (53), 09/30/2025 23:16 (7), 10/29/2025 05:25 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.