How severe is GHSA-wrrw-crp8-979q?

No CVSS score has been assigned to GHSA-wrrw-crp8-979q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wrrw-crp8-979q?

GHSA-wrrw-crp8-979q affects the following packages: pageflow (RubyGems), pageflow (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-wrrw-crp8-979q?

Update pageflow to 14.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wrrw-crp8-979q is resolved across your whole dependency graph.

How do I detect GHSA-wrrw-crp8-979q 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-wrrw-crp8-979q 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-wrrw-crp8-979q?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wrrw-crp8-979q can be triaged on real exposure rather than presence alone.

Is GHSA-wrrw-crp8-979q actively exploited in the wild?

No public exploit code has been indexed for GHSA-wrrw-crp8-979q 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-wrrw-crp8-979q published, and has it been updated?

GHSA-wrrw-crp8-979q 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-wrrw-crp8-979q — pageflow

Fix: codevise/pageflow#1862

GHSA-wrrw-crp8-979q is a security vulnerability in pageflow. A fix is available for pageflow — see the affected versions and patch details below.

Pageflow vulnerable to sensitive user data extraction via Ransack query injection

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

The attack allows extracting sensitive properties of database objects that are associated with users or entries belonging to an account that the attacker has access to.

Pageflow uses the ActiveAdmin Ruby library to provide some management features to its users. ActiveAdmin relies on the Ransack library to implement search functionality. In its default configuration, Ransack will allow for query conditions based on properties of associated database objects [1]. The *_starts_with, *_ends_with or *_contains search matchers [2] can then be abused to exfiltrate sensitive string values of associated database objects via character-by-character brute-force.

[1] https://activerecord-hackery.github.io/ransack/going-further/associations/ [2] https://activerecord-hackery.github.io/ransack/getting-started/search-matches/

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-wrrw-crp8-979q 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-wrrw-crp8-979q can be triaged on real exposure rather than presence alone.

Tailored to GHSA-wrrw-crp8-979q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The attack allows extracting sensitive properties of database objects that are associated with users or entries belonging to an account that the attacker has access to. Pageflow uses the `ActiveAdmin` Ruby library to provide some management features to its users. `ActiveAdmin` relies on the `Ransack` library to implement search functionality. In its default configuration, `Ransack` will allow for query conditions based on properties of associated database objects [1]. The `*_starts_with`, `*_ends_with` or `*_contains` search matchers [2] can then be abused to exfiltrate sensitive

O3 Security · Impact-Aware SCA

Is GHSA-wrrw-crp8-979q in your dependencies?

O3 Security finds GHSA-wrrw-crp8-979q 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