How severe is GHSA-qcqv-38jg-2r43?

No CVSS score has been assigned to GHSA-qcqv-38jg-2r43 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qcqv-38jg-2r43?

GHSA-qcqv-38jg-2r43 affects the following packages: pageflow (RubyGems), pageflow (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-qcqv-38jg-2r43?

Update pageflow to 14.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qcqv-38jg-2r43 is resolved across your whole dependency graph.

How do I detect GHSA-qcqv-38jg-2r43 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pageflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qcqv-38jg-2r43 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-qcqv-38jg-2r43?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qcqv-38jg-2r43 can be triaged on real exposure rather than presence alone.

Is GHSA-qcqv-38jg-2r43 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qcqv-38jg-2r43 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-qcqv-38jg-2r43 published, and has it been updated?

GHSA-qcqv-38jg-2r43 was published on September 15, 2022 and was last updated on December 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

Not in CISA KEV

GHSA-qcqv-38jg-2r43 — pageflow

Fix: codevise/pageflow#1862

GHSA-qcqv-38jg-2r43 is a security vulnerability in pageflow. A fix is available for pageflow — see the affected versions and patch details below.

Pageflow vulnerable to insecure direct object reference in membership update endpoint

Published

Sep 15, 2022

Updated

Dec 6, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Dec 6, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

💎pageflow💎pageflow

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`pageflow`	all versions	14.5.2`bundle update pageflow --conservative`
💎RubyGems	`pageflow`	≥ 15.0.0&&< 15.7.1	15.7.1`bundle update pageflow --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pageflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pageflow to 14.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qcqv-38jg-2r43 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qcqv-38jg-2r43 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-qcqv-38jg-2r43. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-qcqv-38jg-2r43 in your dependencies?

O3 Security finds GHSA-qcqv-38jg-2r43 across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works