# CVE-2026-111875: Databasement missing authorization in scheduled restore

Source: https://junglewise.ai/threats/cve-2026-111875-a-vulnerability-has-been-found-in-david-crty-databasement-up-to  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-18. Updated: 2026-10-18  
License: CC BY 4.0 with a link back

CVE-2026-111875 · Severity: medium · CVSS 4.7 · Published 2026-10-18

Databasement is a self-hosted database backup manager that automates scheduled backups and restores for MySQL, PostgreSQL, MongoDB, and other databases. A missing authorization flaw in the scheduled restore feature allows an attacker to manipulate database schema names without proper permission checks, potentially accessing or modifying backup data they should not be able to reach.

Technologies: [David-Crty Databasement](https://junglewise.ai/threats/technologies/databasement). Vendors: [David-Crty](https://junglewise.ai/threats/vendors/david-crty).

## Quick answers

**Is CVE-2026-111875 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-111875 being exploited in the wild.

**How severe is CVE-2026-111875?** Medium severity, with a CVSS score of 4.7, published 18 October 2026.

**Which products and versions are affected?** David-Crty Databasement up to 1.8.1.

**Is there a fix for CVE-2026-111875?** Yes: fixed in 1.8.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-111875 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-111875?** Check whether you run David-Crty Databasement at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 1.8.2

## Technical details

The vulnerability is a missing authorization (authorization bypass) in the SaveScheduledRestoreRequest API endpoint, specifically in how the schema_name argument is validated. The flaw exists in app/Http/Requests/Api/V1/SaveScheduledRestoreRequest.php and can be exploited remotely without authentication to perform unauthorized restore operations. The fix validates and restricts the schema_name parameter appropriately.

## Affected products

- David-Crty Databasement up to 1.8.1

## Timeline

- 2026-10-18: disclosed
- 2026-09-28: patched: v1.8.2 released

## References

- [https://github.com/David-Crty/databasement/](https://github.com/David-Crty/databasement/)
- [https://github.com/David-Crty/databasement/releases/tag/v1.8.2](https://github.com/David-Crty/databasement/releases/tag/v1.8.2)

## Related threats

- [Databasement authentication bypass in OAuthService](https://junglewise.ai/threats/cve-2026-121939-databasement-before-1-10-9-contains-an-authentication-bypass)
- [databasement argument injection in database backup commands](https://junglewise.ai/threats/cve-2026-108963-databasement-before-1-8-2-allows-remote-code-execution-because)
- [David-Crty databasement improper access control in Snapshot API](https://junglewise.ai/threats/cve-2026-103534-a-vulnerability-was-determined-in-david-crty-databasement-up-to)
- [David-Crty databasement path traversal in RestoreRequest](https://junglewise.ai/threats/cve-2026-103533-a-vulnerability-was-found-in-david-crty-databasement-up-to-1-7-1)
- [Databasement token validation bypass in invitation acceptance](https://junglewise.ai/threats/cve-2026-95654-databasement-before-1-7-14-validates-invitation-tokens-only-when)