CVE-2023-49783 is a medium-severity (CVSS 4.3) CWE-863 vulnerability in silverstripe/admin. A fix is available for silverstripe/admin — see the affected versions and patch details below.
No permission checks for editing/deleting records with CSV import form
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-49783.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
silverstripe/admin🐘silverstripe/adminReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | silverstripe/admin | ≥ 1.0.0&&< 1.13.19 | 1.13.19composer require silverstripe/admin:^1.13.19 |
| 🐘Packagist | silverstripe/admin | ≥ 2.0.0&&< 2.1.8 | 2.1.8composer require silverstripe/admin:^2.1.8 |
Affected Products
adminsilverstripeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/admin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update silverstripe/admin to 1.13.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-49783 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2023-49783 in your dependencies?
Find it across Packagist, including transitive dependencies.