CVE-2025-58067 json
Basecamp's Google Sign-In for Rails allowed redirects to protocol-relative URI
published last yr. modified 22d ago also GHSA-5jch-xhw4-r43v , EUVD-2025-26391
- cvss
- 4.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
Basecamp's Google Sign-In adds Google sign-in to Rails applications. Prior to version 1.3.1, it is possible to redirect a user to another origin if the "proceed_to" value in the session store is set to a protocol-relative URL. Normally the value of this URL is only written and read by the library or the calling application. However, it may be possible to set this session value from a malicious site with a form submission. Any Rails applications using the google_sign_in gem may be vulnerable, if this vector can be chained with another attack that is able to modify the OAuth2 request parameters. This issue has been patched in version 1.3.1. There are no workarounds.
Patch / fix
- rubygems google_sign_in 1.3.1
Is CVE-2025-58067 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N |
| GitHub | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | google_sign_in | <1.3.1 |
1.3.1 |
Affected products
- basecamp google_sign_in
Classification
- Weakness
-
- CWE-601 URL Redirection to Untrusted Site
References
-
github.com
/basecamp/google_sign_in/pull/75
web
-
github.com
/basecamp/google_sign_in/commit/e97aef4626b1bcbd2c6f01f7dd25f12ac855d4cc
web
-
github.com
/basecamp/google_sign_in/security/advisories/GHSA-5jch-xhw4-r43v
web
-
github.com
/basecamp/google_sign_in/releases/tag/v1.3.1
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-58067
advisory
-
github.com
/basecamp/google_sign_in
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/google_sign_in/CVE-2025-58067.yml
web
Sources
- CVE List CVE-2025-58067
- GitHub Advisory GHSA-5jch-xhw4-r43v
- NVD CVE-2025-58067
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.