Live › vulnerability › CVE-2026-111875
Go to dashboardDatabasement up to 1.8.1 has a missing authorization check in its scheduled restore API, reached through the schema_name argument. A remote attacker can trigger scheduled restore actions without the rights they should need.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams that self-host Databasement at version 1.8.1 or earlier and expose its API to users or networks beyond trusted administrators. Instances on or later are not affected by this issue.
1.8.2No product ranges from the sources yet.
1.8.1 are affected.app/Http/Requests/Api/V1/SaveScheduledRestoreRequest.php) to untrusted users.1.8.2 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A vulnerability has been found in David-Crty Databasement up to 1.8.1. Affected by this vulnerability is an unknown functionality of the file app/Http/Requests/Api/V1/SaveScheduledRestoreRequest.php of the component Scheduled Restore. Such manipulation of the argument schema_name leads to missing authorization. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.8.2 addresses this issue. It is suggested to upgrade the affected component.
This page as .md · .json · in your agent: get_signal("CVE-2026-111875")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.