David-Crty Databasement up to 1.8.1 Scheduled Restore SaveScheduledRestoreRequest.php schema_name authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 1.12+ |
Summary
A vulnerability was found in David-Crty Databasement up to 1.8.1. It has been classified as problematic. Affected by this issue is some unknown functionality of the file app/Http/Requests/Api/V1/SaveScheduledRestoreRequest.php of the component Scheduled Restore. Performing a manipulation of the argument schema_name results in authorization. This vulnerability is reported as CVE-2026-111875. The attack is possible to be carried out remotely. Moreover, an exploit is present. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic has been found in David-Crty Databasement up to 1.8.1. This affects an unknown code block of the file app/Http/Requests/Api/V1/SaveScheduledRestoreRequest.php of the component Scheduled Restore. The manipulation of the argument schema_name with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-111875. The exploitability is told to be easy. It is possible to initiate the attack remotely. Additional levels of successful authentication are required for exploitation. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept. By approaching the search of inurl:app/Http/Requests/Api/V1/SaveScheduledRestoreRequest.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.8.2 eliminates this vulnerability. The upgrade is hosted for download at github.com.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.7
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Google Hack: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Databasement 1.8.2
Timeline
10/17/2026 Advisory disclosed10/17/2026 VulDB entry created
10/17/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-3rjj-69wh-r95f
Status: Confirmed
CVE: CVE-2026-111875 (🔒)
GCVE (CVE): GCVE-0-2026-111875
GCVE (VulDB): GCVE-100-421587
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/17/2026 11:53Changes: 10/17/2026 11:53 (60)
Complete: 🔍
Submitter: mikannse
Cache ID: 216::103
Submit
Accepted
- Submit #1005220: David-Crty/databasement databasement <=1.7.3 Write-what-where Condition (by mikannse)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.