CVE-2024-47819
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUmbraco, a free and open source .NET content management system, has a cross-site scripting vulnerability starting in version 14.0.0 and prior to versions 14.3.1 and 15.0.0. 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. Versions 14.3.1 and 15.0.0 contain a patch. As a workaround, ensure that access to the Dictionary section is only granted to trusted users.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stored cross-site scripting (XSS) vulnerability exists in Umbraco CMS versions 14.0.0 through before 14.3.1/15.0.0 in the Dictionary section. Attackers with access to the Dictionary functionality can inject malicious JavaScript that executes when administrative users view the affected content, potentially allowing privilege escalation to admin rights and access to protected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 14.0.0, < 14.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Umbraco versionLocate the version number in your Umbraco installation (typically in the /App_Data/Logs directory, a version file, or the About section in the backoffice), then compare it against the vulnerable range: 14.0.0 through before 14.3.1Affected if The installed version falls within >= 14.0.0 and < 14.3.1
-
Verify Dictionary section accessLog into the Umbraco backoffice and check if the Dictionary section appears in the left navigation menu, or query the users section to see which users have the Dictionary section permission assignedAffected if The Dictionary section is visible and accessible to users in your environment
-
Inspect Dictionary items for unexpected contentNavigate to the Dictionary section in the backoffice and review all dictionary items, looking for entries containing JavaScript tags, event handlers (onclick, onerror, etc.), or unusual encoded content that may contain malicious scriptsAffected if Any dictionary item contains script tags or suspicious JavaScript code that was not authored by trusted administrators
Your environment is affected if you are running Umbraco version 14.0.0 through 14.3.0, the Dictionary section is enabled, and untrusted users have access to create or edit dictionary entries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped14.3.1
Apply the security patch by upgrading to Umbraco versions 14.3.1 or 15.0.0, or implement the workaround of restricting Dictionary section access to only trusted users until the upgrade can be performed.
14.3.1 (or 15.0.0 if available)
- Upgrade Umbraco CMS from any version >= 14.0.0 and < 14.3.1 to version 14.3.1 or later
- If available, also consider upgrading to version 15.0.0 for the latest stable release
- After upgrading, verify that the Dictionary section functionality works correctly
- Review user permissions to ensure only trusted users have access to sensitive sections, as a defense-in-depth measure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47819 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47819 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data