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