# CVE-2026-103534: David-Crty databasement improper access control in Snapshot API

Source: https://junglewise.ai/threats/cve-2026-103534-a-vulnerability-was-determined-in-david-crty-databasement-up-to  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-01. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-103534 · Severity: medium · CVSS 6.3 · Published 2026-10-01

databasement is a self-hosted database backup manager that stores critical backups for MySQL, PostgreSQL, MongoDB, and other databases. An improper access control vulnerability in the Snapshot API allows remote attackers to view snapshots they should not have access to, potentially exposing sensitive backup data without authentication barriers or proper authorization checks.

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-103534 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-103534 being exploited in the wild.

**How severe is CVE-2026-103534?** Medium severity, with a CVSS score of 6.3, published 1 October 2026.

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

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

**How is CVE-2026-103534 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-103534?** 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.7.2

## Technical details

The vulnerability is an improper access control flaw in the SnapshotPolicy.viewAny and SnapshotPolicy.view functions within the /api/v1/snapshots endpoint of the Snapshot Model component. The vulnerability allows remote exploitation without requiring prior authentication. The flaw has been patched in version 1.7.2 through hardened organization scoping and path validation.

## Affected products

- David-Crty databasement up to 1.7.1

## Timeline

- 2026-10-01: disclosed: Vulnerability publicly disclosed
- 2026-08-04: patched: Fix released in version 1.7.2

## References

- [https://github.com/David-Crty/databasement/](https://github.com/David-Crty/databasement/)
- [https://github.com/David-Crty/databasement/releases/tag/v1.7.2](https://github.com/David-Crty/databasement/releases/tag/v1.7.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 missing authorization in scheduled restore](https://junglewise.ai/threats/cve-2026-111875-a-vulnerability-has-been-found-in-david-crty-databasement-up-to)
- [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 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)