GHSA-2m5g-8xpw-42vp is a high-severity (CVSS 8.9) vulnerability in cartalyst/sentry. A fix is available for cartalyst/sentry — see the affected versions and patch details below.
OpenCFP Framework (Sentry) Account takeover via null password reset codes
Real-World Exposure
cartalyst/sentryReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
OpenCFP, an open-source conference talk submission system written in PHP, contains a security vulnerability in its third-party authentication framework, Sentry, developed by Cartalyst. The vulnerability stems from how Sentry handles password reset checks. Users lacking a password reset token stored in the database default to having NULL in the reset_password_code column. Exploiting this flaw could allow unauthorized manipulation of any OpenCFP user's password, particularly those without an unused password reset token. Although successful login still requires correlating the numeric user ID with an email address, the identification of likely organizers (users 1-5) may facilitate this process.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | cartalyst/sentry | all versions | 2.1.7composer require cartalyst/sentry:^2.1.7 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cartalyst/sentry, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cartalyst/sentry to 2.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2m5g-8xpw-42vp 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-2m5g-8xpw-42vp can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2m5g-8xpw-42vp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2m5g-8xpw-42vp in your dependencies?
O3 Security finds GHSA-2m5g-8xpw-42vp across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.