# CVE-2024-48926: Umbraco CMS logout page displayed before session expiration

> Attackers can exploit a timing gap where the logout page appears before session expiration, potentially allowing unauthorized access during the delay.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Oct 2024
- **Updated:** 22 Oct 2024
- **Also known as:** GHSA-fp6q-gccw-7qqm

## What is CVE-2024-48926?

CVE-2024-48926 is a medium-severity vulnerability in Umbraco Umbraco Cms, published on 22 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Umbraco, a free and open source .NET content management system, has an insufficient session expiration issue in versions on the 13.x branch prior to 13.5.2, 10.x prior to 10.8.7, and 8.x prior to 8.18.15. The Backoffice displays the logout page with a session timeout message before the server session has fully expired, causing users to believe they have been logged out approximately 30 seconds before they actually are. Versions 13.5.2, 10.8,7, and 8.18.15 contain a patch for the issue.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2024-48926?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Umbraco.CMS` | NuGet | From 10.0.0 | 10.8.7 |
| `Umbraco.CMS` | NuGet | From 10.0.0 | 10.8.7 |
| `Umbraco.CMS` | NuGet | From 13.0.0 | 13.5.2 |
| `Umbraco.CMS` | NuGet | From 13.0.0 | 13.5.2 |
| `UmbracoCMS` | NuGet | From 8.0.0 | 8.18.15 |
| `UmbracoCMS` | NuGet | From 8.0.0 | 8.18.15 |

Products: Umbraco Umbraco Cms.

## How do I fix CVE-2024-48926?

Upgrade Umbraco.CMS to a fixed version for your release line: 10.8.7 or 13.5.2.

## Is CVE-2024-48926 being exploited?

There is no known exploitation of CVE-2024-48926 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-2024-48926 and fix it if it is affected.

What it is: CVE-2024-48926 is a medium-severity vulnerability in Umbraco Umbraco Cms, published on 22 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-48926 in the wild and no public exploit code.

Affected packages and fixed versions:
- Umbraco.CMS (NuGet): affected from 10.0.0; fixed in 10.8.7
- Umbraco.CMS (NuGet): affected from 10.0.0; fixed in 10.8.7
- Umbraco.CMS (NuGet): affected from 13.0.0; fixed in 13.5.2
- Umbraco.CMS (NuGet): affected from 13.0.0; fixed in 13.5.2
- UmbracoCMS (NuGet): affected from 8.0.0; fixed in 8.18.15
- UmbracoCMS (NuGet): affected from 8.0.0; fixed in 8.18.15

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

## Sources

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

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