CVE-2023-48227 json
Umbraco CMS Backoffice User can bypass "Publish" restriction
published 2023-12-12 2 y ago modified 2026-09-10 1 mo ago also GHSA-335x-5wcm-8jv2 , EUVD-2023-3077
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Umbraco is an ASP.NET content management system (CMS). Starting in version 8.0.0 and prior to versions 8.18.10, 10.7.0, and 12.3.0, Backoffice users with send for approval permission but not publish permission are able to publish in some scenarios. Versions 8.18.10, 10.7.0, and 12.3.0 contains a patch for this issue. No known workarounds are available.
Patch / fix
- nuget Umbraco.CMS 8.18.10, 10.8.0, 12.3.0
- umbraco umbraco_cms 8.18.10, 10.7.0, 12.3.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| GitHub | 3.1 | 0.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | Umbraco.CMS | >=8.0.0, <8.18.10 >=9.0.0, <10.8.0 >=11.0.0, <12.3.0 |
8.18.10 10.8.0 12.3.0 |
Affected products
- umbraco Umbraco-CMS
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
github.com
/umbraco/Umbraco-CMS/security/advisories/GHSA-335x-5wcm-8jv2
web, url-repurposed
-
nvd.nist.gov
/vuln/detail/CVE-2023-48227
advisory
-
github.com
/umbraco/Umbraco-CMS
package
Sources
- CVE List CVE-2023-48227
- GitHub Advisory GHSA-335x-5wcm-8jv2
- NVD CVE-2023-48227
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.