Skip to content

Pageflow vulnerable to insecure direct object reference in membership update endpoint

High severity GitHub Reviewed Published Sep 14, 2022 in codevise/pageflow • Updated Jan 10, 2023

Package

bundler pageflow (RubyGems)

Affected versions

< 14.5.2
>= 15.0.0, < 15.7.1

Patched versions

14.5.2
15.7.1

Description

Impact

Pageflow has a membership edit feature which allows users to edit the roles of user memberships associated with an account that they have the manager role to (including their own). While the Entity dropdown select field is greyed out in the UI, an attacker can use tools which allow sending arbitrary HTTP request to craft a request to the /admin/users/{user_id}/memberships/{membership_id} endpoint containing an additional membership[entity_id] parameter. This parameter is honored when the membership is updated, allowing an attacker to update the membership object associated with their own account (with manager role) to be associated with a different attacker-chosen account instead. Since account_ids are enumerable, an attacker can compromise all accounts present on the platform.

Mitigation

Upgrade to version 15.7.1 or 14.5.2 of the pageflow gem.

For more information

If you have any questions or comments about this advisory email us at info(at)codevise.de

Credits

Positive Security

References

@tf tf published to codevise/pageflow Sep 14, 2022
Published to the GitHub Advisory Database Sep 15, 2022
Reviewed Sep 15, 2022
Last updated Jan 10, 2023

Severity

High

Weaknesses

No CWEs

CVE ID

No known CVE

GHSA ID

GHSA-qcqv-38jg-2r43

Source code

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