Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-111875 Overview
CVE-2026-111875 is a missing authorization vulnerability [CWE-862] in David-Crty Databasement versions up to 1.8.1. The flaw resides in the app/Http/Requests/Api/V1/SaveScheduledRestoreRequest.php file within the Scheduled Restore component. Manipulation of the schema_name argument bypasses authorization controls, allowing an authenticated attacker to perform restore operations outside their intended scope. The attack is executable remotely over the network. The exploit has been disclosed publicly. Upgrading to version 1.8.2 resolves the issue.
Critical Impact
Authenticated remote attackers can manipulate the schema_name parameter to bypass authorization checks on scheduled database restore operations, affecting confidentiality, integrity, and availability of targeted schemas.
Affected Products
- David-Crty Databasement versions up to and including 1.8.1
- Component: Scheduled Restore (SaveScheduledRestoreRequest.php)
- Fixed in David-Crty Databasement version 1.8.2
Discovery Timeline
- 2026-10-18 - CVE-2026-111875 published to NVD
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-111875
Vulnerability Analysis
The vulnerability is a missing authorization flaw [CWE-862] in the Scheduled Restore feature of Databasement. The request validation class SaveScheduledRestoreRequest.php under app/Http/Requests/Api/V1/ processes a schema_name parameter without verifying that the requesting user has permission to operate on the specified schema. An authenticated user with low-tier access can submit a crafted request targeting schemas outside their authorized scope. The impact spans confidentiality, integrity, and availability at a limited level, as unauthorized restore scheduling can overwrite or expose database content.
Root Cause
The root cause is the absence of an authorization check on the schema_name input within the Scheduled Restore request handler. Laravel-style FormRequest classes typically enforce access control through an authorize() method or explicit policy checks. In Databasement 1.8.1 and earlier, that enforcement is missing or incomplete for schema_name, meaning any authenticated caller passing input validation can schedule restores against arbitrary schemas.
Attack Vector
An attacker with authenticated access sends a crafted HTTP request to the Scheduled Restore API endpoint. The request includes a schema_name value referencing a schema the attacker should not control. Because the application does not validate ownership or role against that schema, the restore job is accepted and queued. Exploitation requires network access to the API and valid credentials, but no user interaction. See the GitHub Security Advisory GHSA-3rjj-69wh-r95f for additional technical context.
// No verified proof-of-concept code is published for this CVE.
// Refer to the vendor advisory and commit history for v1.8.2 for exact patch details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-111875
Indicators of Compromise
- Unexpected scheduled restore jobs targeting schemas not owned by the submitting user account
- API requests to the Scheduled Restore endpoint containing schema_name values inconsistent with the caller's role or tenant
- Database restore activity originating from low-privilege service accounts
Detection Strategies
- Review application logs for POST requests handled by SaveScheduledRestoreRequest and correlate the schema_name parameter with the authenticated user's assigned schemas
- Enable audit logging on the Databasement API tier and alert on restore scheduling events outside normal operator accounts
- Compare job queue entries against an allowlist of expected user-to-schema relationships
Monitoring Recommendations
- Monitor the Databasement job queue for restore tasks created outside maintenance windows
- Track changes to database schemas following API-initiated restore jobs
- Alert on repeated 2xx responses to the Scheduled Restore endpoint from a single low-privilege account
How to Mitigate CVE-2026-111875
Immediate Actions Required
- Upgrade Databasement to version 1.8.2 or later, which contains the authorization fix
- Audit existing scheduled restore jobs and remove any that reference schemas inconsistent with the creator's role
- Rotate credentials for any accounts that interacted with the Scheduled Restore endpoint prior to patching
Patch Information
The maintainer addressed the issue in GitHub Release v1.8.2. Review the GitHub Project Repository and the GitHub Security Advisory GHSA-3rjj-69wh-r95f for release notes and commit references. Additional vulnerability metadata is available at VulDB CVE-2026-111875.
Workarounds
- Restrict access to the Scheduled Restore API endpoint using network-level controls or a reverse proxy until the upgrade is deployed
- Limit API credentials to accounts that require restore scheduling and revoke the capability from general-purpose users
- Apply an authorization check at the web server or API gateway tier that validates schema_name against the authenticated identity
# Example reverse proxy restriction (nginx) for the Scheduled Restore endpoint
location /api/v1/scheduled-restores {
allow 10.0.0.0/24; # restrict to maintenance subnet
deny all;
proxy_pass http://databasement_backend;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

