First published: Tue Dec 12 2023(Updated: )
#### Impact Backoffice users with send for approval permission but not publish permission are able to publish in some scenarios. #### Explanation of the vulnerability Backoffice users without permission to publish content, but only to send for approval, can bypass the restriction by modifying the request body of the "Send for Approval" request.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
nuget/Umbraco.CMS | >=11.0.0<12.3.0 | 12.3.0 |
nuget/Umbraco.CMS | >=9.0.0<10.8.0 | 10.8.0 |
nuget/Umbraco.CMS | >=8.0.0<8.18.10 | 8.18.10 |
Umbraco CMS | >=8.0.0<8.18.10 | |
Umbraco CMS | >=9.0.0<10.7.0 | |
Umbraco CMS | >=11.0.0<12.3.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-48227 has a moderate severity level due to the potential for unauthorized content publication.
To fix CVE-2023-48227, update to Umbraco CMS version 12.3.0, 10.8.0, or 8.18.10 as applicable.
Backoffice users of Umbraco CMS versions between 8.0.0 and 12.3.0 with send for approval permissions but lacking publish permissions are affected.
Attackers can exploit CVE-2023-48227 to publish content despite lacking the intended permissions.
CVE-2023-48227 was disclosed in 2023 as part of a vulnerability advisory regarding Umbraco CMS.