# CVE-2023-48227: Umbraco CMS Backoffice User can bypass "Publish" restriction

> Backoffice users with send-for-approval permissions can bypass restrictions to publish content, allowing unauthorized data modification.

- **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:** 12 Dec 2023
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-335x-5wcm-8jv2

## What is CVE-2023-48227?

CVE-2023-48227 is a medium-severity missing authorization vulnerability in Umbraco Umbraco Cms, published on 12 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

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

6 open source packages ship an affected version, including Umbraco.CMS. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Umbraco.CMS` | NuGet | From 11.0.0 | 12.3.0 |
| `Umbraco.CMS` | NuGet | From 11.0.0 | 12.3.0 |
| `Umbraco.CMS` | NuGet | From 8.0.0 | 8.18.10 |
| `Umbraco.CMS` | NuGet | From 8.0.0 | 8.18.10 |
| `Umbraco.CMS` | NuGet | From 9.0.0 | 10.8.0 |
| `Umbraco.CMS` | NuGet | From 9.0.0 | 10.8.0 |

Products: Umbraco Umbraco Cms.

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

Upgrade Umbraco.CMS to a fixed version for your release line: 12.3.0, 8.18.10 or 10.8.0.

## Is CVE-2023-48227 being exploited?

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

## Other vulnerabilities in Umbraco Umbraco Cms

- [CVE-2025-67288](https://insights.sbomify.com/CVE-2025-67288/): Umbraco CMS has an arbitrary file upload vulnerability (critical 10.0)
- [CVE-2014-10074](https://insights.sbomify.com/CVE-2014-10074/): File upload in n/a (critical 9.8)
- [CVE-2012-1301](https://insights.sbomify.com/CVE-2012-1301/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2012-10054](https://insights.sbomify.com/CVE-2012-10054/): Umbraco CMS < 4.7.1 codeEditorSave.asmx RCE (critical 9.3)
- [CVE-2025-32017](https://insights.sbomify.com/CVE-2025-32017/): Umbraco has a Management API Vulnerability to Path Traversal With Authenticated Users (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-48227 is a medium-severity missing authorization vulnerability in Umbraco Umbraco Cms, published on 12 Dec 2023. 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-48227 in the wild and no public exploit code.

Affected packages and fixed versions:
- Umbraco.CMS (NuGet): affected from 11.0.0; fixed in 12.3.0
- Umbraco.CMS (NuGet): affected from 11.0.0; fixed in 12.3.0
- Umbraco.CMS (NuGet): affected from 8.0.0; fixed in 8.18.10
- Umbraco.CMS (NuGet): affected from 8.0.0; fixed in 8.18.10
- Umbraco.CMS (NuGet): affected from 9.0.0; fixed in 10.8.0
- Umbraco.CMS (NuGet): affected from 9.0.0; fixed in 10.8.0

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-48227/ (Markdown: https://insights.sbomify.com/CVE-2023-48227/index.md)
```

## Sources

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

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