CVE-2023-49273
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.4, users with low privileges (Editor, etc.) are able to access some unintended endpoints. Versions 8.18.10, 10.8.1, and 12.3.4 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 confidenceIn Umbraco CMS versions 8.0.0 through 8.18.9, 10.8.0, and 12.3.3, users with low-privilege roles such as Editor can access endpoints that should be restricted to higher-privilege users. This is a broken access control vulnerability where authorization checks are insufficient for certain API endpoints.
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.4CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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.
-
Determine installed Umbraco versionCheck the version number in your Umbraco installation. In version 8, look at the assembly version of Umbraco.dll or check the /umbraco/version.txt file. In versions 10 and 12, check the project file or the installed NuGet package version.Affected if The installed version falls within 8.0.0 to 8.18.9, 10.0.0 to 10.8.0, or 12.0.0 to 12.3.3.
-
Identify user roles with low privilegesLog into the Umbraco backoffice and navigate to the Users or Members section. Check for users assigned to roles such as Editor, Writer, or other low-privilege roles that should have restricted access.Affected if Low-privilege roles such as Editor exist in the system and are assigned to active users.
-
Verify API endpoint accessibilityAttempt to access restricted API endpoints using an account with a low-privilege role (such as Editor). The vulnerability allows these accounts to access endpoints that should require higher privilege levels, such as those meant for Administrators or Translators.Affected if A user with Editor or similar low-privilege role can successfully access endpoints that should be restricted to Administrators or higher-privilege roles.
-
Review role permissions configurationIn the Umbraco backoffice, go to the Users > Users Groups section. Examine the permissions assigned to each role, particularly checking whether Editor or similar roles have unintended access to sensitive API operations.Affected if Editor or low-privilege roles have permissions to access API actions or controllers that should be restricted to higher-privilege roles.
You are affected if your Umbraco installation version is 8.0.0-8.18.9, 10.0.0-10.8.0, or 12.0.0-12.3.3 AND low-privilege users can access API endpoints intended for higher-privilege roles.
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.4
Upgrade Umbraco to version 8.18.10, 10.8.1, or 12.3.4 (or later) to apply the patch that enforces proper authorization on the affected endpoints.
Umbraco CMS 8.18.10 (for v8 branch), 10.8.1 (for v10 branch), or 12.3.4 (for v12 branch)
- Identify the current Umbraco version by checking the project configuration or Umbraco backoffice (Help > About)
- Determine which major version branch (8.x, 10.x, or 12.x) is currently in use
- Backup the entire project including database and all configuration files
- Update NuGet package references to the appropriate fixed version: for v8 upgrade to 8.18.10, for v10 upgrade to 10.8.1, or for v12 upgrade to 12.3.4
- Run dotnet restore to fetch the updated packages
- Rebuild the solution to ensure all dependencies resolve correctly
- Deploy the updated application to a staging environment for testing
- Verify that low-privilege users (Editor role) can no longer access the unintended endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49273 — 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-49273 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