basecamp google_sign_in up to 1.3.0 proceed_to redirect

Summaryinfo

A vulnerability classified as problematic was found in basecamp google_sign_in up to 1.3.0. This affects an unknown part. The manipulation of the argument proceed_to results in redirect. This vulnerability is reported as CVE-2025-58067. The attack can be launched remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in basecamp google_sign_in up to 1.3.0. It has been classified as problematic. Affected is an unknown function. The manipulation of the argument proceed_to with an unknown input leads to a redirect vulnerability. CWE is classifying the issue as CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. This is going to have an impact on integrity. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2025-58067 since 08/22/2025. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1204.001.

Upgrading to version 1.3.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch e97aef4626b1bcbd2c6f01f7dd25f12ac855d4cc is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• basecamp

Name

• google_sign_in

Version

• 1.0
• 1.1
• 1.2
• 1.3.0

License

• open-source

Website

• Product: https://github.com/basecamp/google_sign_in/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion