CVE-2023-49089
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 is an ASP.NET content management system (CMS). Starting in version 8.0.0 and prior to versions 8.18.10, 10.8.1, and 12.3.0, Backoffice users with permissions to create packages can use path traversal and thereby write outside of the expected location. Versions 8.18.10, 10.8.1, and 12.3.0 contain a patch for this issue.
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 confidencePath traversal vulnerability in Umbraco CMS allows authenticated backoffice users with package creation permissions to write files outside the intended directory by manipulating file paths during package creation. This is a directory traversal issue in the package creation feature.
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>= 8.0.0, < 8.18.10>= 10.0.0, < 10.8.1>= 12.0.0, < 12.3.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Identify the installed Umbraco versionCheck the version from the web.config file, the ~/bin/Umbraco.Core.dll file properties, or log into the backoffice and navigate to the About/Version section in the Help drawerAffected if The installed version is 8.0.0 through 8.18.9, 10.0.0 through 10.8.0, or 12.0.0 through 12.2.0 (any version less than 8.18.10, 10.8.1, or 12.3.0 respectively)
-
Verify if package creation permissions existIn the Umbraco backoffice, go to the Users section and review the roles or groups assigned to each user. Check if any role includes the 'Packages' or 'Create Package' permission under the Access permissionsAffected if Any user account has been granted package creation or package management permissions in the backoffice
-
Review recent package creation activityCheck the ~/App_Data/Packages/ directory for any package zip files. Also review server file logs and the Umbraco audit log (if enabled) for package creation events around the time of suspected exploitationAffected if Any unexpected package files exist outside the intended ~/App_Data/Packages/ directory, or if package creation activity was performed by an untrusted user
-
Inspect web server write locationsUse file system auditing or review the web server logs to identify any file write operations to directories outside the expected Umbraco application folders (such as the root web directory or system directories) that coincide with package creation feature usageAffected if Files were written to directories outside the intended App_Data/Packages/ path after package creation feature was used
You are affected if your Umbraco installation version is below 8.18.10, 10.8.1, or 12.3.0 AND any backoffice user has package creation permissions, regardless of whether exploitation has occurred.
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 · scoped8.18.1010.8.112.3.0
Upgrade to Umbraco versions 8.18.10, 10.8.1, or 12.3.0 (or later). Until patching is possible, restrict package creation permissions to only highly trusted administrators.
Umbraco CMS 8.18.10 (for 8.x), 10.8.1 (for 10.x), or 12.3.0 (for 12.x)
- Backup your Umbraco database and application files before proceeding with any upgrade
- Identify your current Umbraco version by checking the /Properties/AssemblyInfo.cs or your project references
- For Umbraco 8.x installations: Upgrade to version 8.18.10 or later by updating the UmbracoCms package reference in your .csproj file
- For Umbraco 10.x installations: Upgrade to version 10.8.1 or later by updating the UmbracoCms package reference in your .csproj file
- For Umbraco 12.x installations: Upgrade to version 12.3.0 or later by updating the UmbracoCms package reference in your .csproj file
- Run dotnet restore to fetch the new package versions
- Rebuild and test your solution locally before deploying to production
- Deploy the updated application to your environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49089 — 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-2023-49089 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