Summary
Pageflow vulnerable to insecure direct object reference in membership update endpoint
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
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
pageflow to 14.5.2 or later; pageflow to 15.7.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-QCQV-38JG-2R43? GHSA-QCQV-38JG-2R43 is a high-severity security vulnerability in pageflow (rubygems), affecting versions < 14.5.2. It is fixed in 14.5.2, 15.7.1.
- Which versions of pageflow are affected by GHSA-QCQV-38JG-2R43? pageflow (rubygems) versions < 14.5.2 is affected.
- Is there a fix for GHSA-QCQV-38JG-2R43? Yes. GHSA-QCQV-38JG-2R43 is fixed in 14.5.2, 15.7.1. Upgrade to this version or later.
- Is GHSA-QCQV-38JG-2R43 exploitable, and should I be worried? Whether GHSA-QCQV-38JG-2R43 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-QCQV-38JG-2R43 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-QCQV-38JG-2R43?
- Upgrade
pageflowto 14.5.2 or later - Upgrade
pageflowto 15.7.1 or later
- Upgrade