CI4MS: Arbitrary Database Table Drop via Theme deleteProcess
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| ci4-cms-erp | ci4ms | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Ci4-cms-erp | Ci4ms |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-vgrf-pr28-vf98 | CI4MS Vulnerable to Arbitrary Database Table Drop via Theme deleteProcess |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.409% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ci4-cms-erp
Ci4-cms-erp ci4ms |
|
| Vendors & Products |
Ci4-cms-erp
Ci4-cms-erp ci4ms |
| 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
|