Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm.NET NuGet

GHSA-c5g6-6xf7-qxp3

MEDIUM

Umbraco CMS vulnerable to stored Cross-site Scripting in the "dictionary name" on Dictionary section

Also known asCVE-2024-47819
Published
Oct 22, 2024
Updated
Oct 22, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk24th percentile-0.24%
0.00%0.36%0.71%1.07%0.5%0.3%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@umbraco-cms/backofficenpm
6Kdownloads / week

Description

Impact

This can be leveraged to gain access to higher-privilege endpoints, e.g. if you get a user with admin privileges to run the code, you can potentially elevate all users and grant them admin privileges or access protected content.

Patches

Will be patched in 14.3.1 and 15.0.0.

Workarounds

Ensure that access to the Dictionary section is only granted to trusted users.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npm@umbraco-cms/backoffice14.0.0&&< 14.3.114.3.1
.NETNuGetUmbraco.Cms.StaticAssets14.0.0&&< 14.3.114.3.1

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/backoffice. 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/backoffice to 14.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c5g6-6xf7-qxp3 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 GHSA-c5g6-6xf7-qxp3 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 GHSA-c5g6-6xf7-qxp3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact This can be leveraged to gain access to higher-privilege endpoints, e.g. if you get a user with admin privileges to run the code, you can potentially elevate all users and grant them admin privileges or access protected content. ### Patches Will be patched in 14.3.1 and 15.0.0. ### Workarounds Ensure that access to the Dictionary section is only granted to trusted users.
O3 Security · Impact-Aware SCA

Is GHSA-c5g6-6xf7-qxp3 in your dependencies?

O3 detects GHSA-c5g6-6xf7-qxp3 across npm, NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.