Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-vgrf-pr28-vf98 | CI4MS Vulnerable to Arbitrary Database Table Drop via Theme deleteProcess |
Thu, 07 May 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 07 May 2026 06:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ci4-cms-erp
Ci4-cms-erp ci4ms |
|
| Vendors & Products |
Ci4-cms-erp
Ci4-cms-erp ci4ms |
Thu, 07 May 2026 04:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | CI4MS is a CodeIgniter 4-based CMS skeleton that delivers a production-ready, modular architecture with RBAC authorization and theme support. From version 0.31.1.0 to before version 0.31.8.0, the deleteProcess() action accepts a POST parameter tables[] containing arbitrary table names. These are passed directly to $forge->dropTable() without validating that the tables belong to the theme being deleted. The deleteConfirm view correctly populates tables[] from the theme's own migration files, but the server-side deleteProcess does not verify the received values against those files. An authenticated admin can craft a POST request with arbitrary table names and drop any table in the database. This issue has been patched in version 0.31.8.0. | |
| Title | CI4MS: Arbitrary Database Table Drop via Theme deleteProcess | |
| Weaknesses | CWE-20 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-07T13:42:35.440Z
Reserved: 2026-04-22T15:11:54.671Z
Link: CVE-2026-41890
Updated: 2026-05-07T13:42:20.320Z
Status : Deferred
Published: 2026-05-07T04:16:33.740
Modified: 2026-05-07T15:16:09.530
Link: CVE-2026-41890
No data.
OpenCVE Enrichment
Updated: 2026-05-07T06:15:23Z
Github GHSA