Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet
Not in CISA KEV

CVE-2024-10761

CVE-2024-10761 is a Cross-site Scripting (XSS) vulnerability in Umbraco.Cms. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2024-10761 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Umbraco CMS Dashboard frame cross site scripting

Also known asGHSA-69cg-w8vm-h229
Published
Nov 4, 2024
Updated
Jul 15, 2026
Affected
8 pkgs
Patched
8 / 8
Exploits
1 known
Exploitation data as of Jul 15, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

8 pkgs affected
.NETUmbraco.Cms.NETUmbraco.Cms.NETUmbraco.Cms.NETUmbraco.Cms.NETUmbraco.Cms.Web.Common.NETUmbraco.Cms.Web.Common.NETUmbraco.Cms.Web.Common.NETUmbraco.Cms.Web.Common

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability was found in Umbraco CMS up to 10.7.7/12.3.6/13.5.2/14.3.1/15.1.1. It has been classified as problematic. Affected is an unknown function of the file /Umbraco/preview/frame?id{} of the component Dashboard. The manipulation of the argument culture leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 10.8.8, 13.5.3, 14.3.2 and 15.1.2 is able to address this issue. It is recommended to upgrade the affected component.

Affected Packages

8 total 8 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetUmbraco.Cms11.0.0&&< 13.5.313.5.3
.NETNuGetUmbraco.Cms14.0.0&&< 14.3.214.3.2
.NETNuGetUmbraco.Cms15.0.0&&< 15.1.215.1.2
.NETNuGetUmbraco.Cms10.8.7&&< 10.8.810.8.8
.NETNuGetUmbraco.Cms.Web.Common11.0.0&&< 13.5.313.5.3
.NETNuGetUmbraco.Cms.Web.Common14.0.0&&< 14.3.214.3.2
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Umbraco.Cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update Umbraco.Cms to 13.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-10761 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-10761 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-10761. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability was found in Umbraco CMS up to 10.7.7/12.3.6/13.5.2/14.3.1/15.1.1. It has been classified as problematic. Affected is an unknown function of the file /Umbraco/preview/frame?id{} of the component Dashboard. The manipulation of the argument culture leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 10.8.8, 13.5.3, 14.3.2 and 15.1.2 is able to address this issue. It is recommended to upgrade the affected component.
O3 Security · Impact-Aware SCA

Is CVE-2024-10761 in your dependencies?

O3 detects CVE-2024-10761 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.