# CVE-2023-49783: No permission checks for editing/deleting records with CSV import form

> Users with create permissions can edit or delete records via CSV import despite lacking edit or delete permissions in Silverstripe Admin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-j3m6-gvm8-mhvw

## What is CVE-2023-49783?

CVE-2023-49783 is a medium-severity missing authorization vulnerability in silverstripe-admin, published on 23 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Silverstripe Admin provides a basic management interface for the Silverstripe Framework. In versions on the 1.x branch prior to 1.13.19 and on the 2.x branch prior to 2.1.8, users who don't have edit or delete permissions for records exposed in a `ModelAdmin` can still edit or delete records using the CSV import form, provided they have create permissions. The likelihood of a user having create permissions but not having edit or delete permissions is low, but it is possible. Note that this doesn't affect any `ModelAdmin` which has had the import form disabled via the `showImportForm` public property. Versions 1.13.19 and 2.1.8 contain a patch for the issue. Those who have a custom implementation of `BulkLoader` should update their implementations to respect permissions when the return value of `getCheckPermissions()` is true. Those who use any `BulkLoader` in their own project logic, or maintain a module which uses it, should consider passing `true` to `setCheckPermissions()` if the data is provided by users.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2023-49783?

4 open source packages ship an affected version, including silverstripe/admin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/admin` | Packagist | From 1.0.0 | 1.13.19 |
| `silverstripe/admin` | Packagist | From 1.0.0 | 1.13.19 |
| `silverstripe/admin` | Packagist | From 2.0.0 | 2.1.8 |
| `silverstripe/admin` | Packagist | From 2.0.0 | 2.1.8 |

Products: Silverstripe Admin.

## How do I fix CVE-2023-49783?

Upgrade silverstripe/admin to a fixed version for your release line: 1.13.19 or 2.1.8.

## Is CVE-2023-49783 being exploited?

There is no known exploitation of CVE-2023-49783 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49783 and fix it if it is affected.

What it is: CVE-2023-49783 is a medium-severity missing authorization vulnerability in silverstripe-admin, published on 23 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-49783 in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/admin (Packagist): affected from 1.0.0; fixed in 1.13.19
- silverstripe/admin (Packagist): affected from 1.0.0; fixed in 1.13.19
- silverstripe/admin (Packagist): affected from 2.0.0; fixed in 2.1.8
- silverstripe/admin (Packagist): affected from 2.0.0; fixed in 2.1.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-49783/ (Markdown: https://insights.sbomify.com/CVE-2023-49783/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-49783
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-49783
- OSV: https://osv.dev/vulnerability/CVE-2023-49783

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-49783/
Summaries are generated and may contain mistakes; the official description above is the record.