Skip to content

Backoffice User can bypass "Publish" restriction

Low severity GitHub Reviewed Published Dec 12, 2023 in umbraco/Umbraco-CMS • Updated Jan 12, 2024

Package

nuget Umbraco.CMS (NuGet)

Affected versions

>= 8.0.0, < 8.18.10
>= 9.0.0, < 10.8.0
>= 11.0.0, < 12.3.0

Patched versions

8.18.10
10.8.0
12.3.0

Description

Impact

Backoffice users with send for approval permission but not publish permission are able to publish in some scenarios.

Explanation of the vulnerability

Backoffice users without permission to publish content, but only to send for approval, can bypass the restriction by modifying the request body of the "Send for Approval" request.

References

@bergmania bergmania published to umbraco/Umbraco-CMS Dec 12, 2023
Published by the National Vulnerability Database Dec 12, 2023
Published to the GitHub Advisory Database Dec 13, 2023
Reviewed Dec 13, 2023
Last updated Jan 12, 2024

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N

EPSS score

0.053%
(23rd percentile)

Weaknesses

CVE ID

CVE-2023-48227

GHSA ID

GHSA-335x-5wcm-8jv2

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.