Skip to content

Improper Handling of Insufficient Permissions in `wagtail.contrib.settings`

Moderate severity GitHub Reviewed Published May 30, 2024 in wagtail/wagtail • Updated Jun 3, 2024

Package

pip wagtail (pip)

Affected versions

>= 6.0.0, < 6.0.5
>= 6.1.0, < 6.1.2

Patched versions

6.0.5
6.1.2

Description

Impact

Due to an improperly applied permission check in the wagtail.contrib.settings module, a user with access to the Wagtail admin and knowledge of the URL of the edit view for a settings model can access and update that setting, even when they have not been granted permission over the model. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.

Patches

Patched versions have been released as Wagtail 6.0.5 and 6.1.2. Wagtail releases prior to 6.0 are unaffected.

Workarounds

No workaround is available.

Acknowledgements

Many thanks to Victor Miti for reporting this issue.

For more information

If you have any questions or comments about this advisory:

References

@laymonage laymonage published to wagtail/wagtail May 30, 2024
Published by the National Vulnerability Database May 30, 2024
Published to the GitHub Advisory Database Jun 2, 2024
Reviewed Jun 2, 2024
Last updated Jun 3, 2024

Severity

Moderate

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
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
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:H/UI:N/S:U/C:L/I:H/A:N

EPSS score

0.043%
(10th percentile)

Weaknesses

CVE ID

CVE-2024-35228

GHSA ID

GHSA-xxfm-vmcf-g33f

Source code

Credits

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