GHSA-g6f5-4w43-2x63 is a medium-severity (CVSS 6.1) vulnerability in socalnick/scn-social-auth. A fix is available for socalnick/scn-social-auth — see the affected versions and patch details below.
ScnSocialAuth Cross-site Scripting vulnerability in login redirect param
Real-World Exposure
socalnick/scn-social-authReal-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
ScnSocialAuth version 1.15.2 has been released and includes a security for this vulnerability. Fix has been applied in https://github.com/SocalNick/ScnSocialAuth/commit/4a00966c41bc37251586d007564c5c891eba3700
Affected versions
All versions below 1.15.2 are affected. dev-master is fixed starting from https://github.com/SocalNick/ScnSocialAuth/commit/4a00966c41bc37251586d007564c5c891eba3700
Exploits
Because of missing escaping of the URL param redirect a XSS attack is possible.
For example: Setting the redirect param to "><a%20href="http://github.com">GitHub.com</a><inpu%20type="hidden"%20" would result in a link added to the login page.
Resolution
If you are using any version of ScnSocialAuth below 1.15.2 please upgrade immediately by running composer update.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | socalnick/scn-social-auth | all versions | 1.15.2composer require socalnick/scn-social-auth:^1.15.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for socalnick/scn-social-auth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update socalnick/scn-social-auth to 1.15.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g6f5-4w43-2x63 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-g6f5-4w43-2x63 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-g6f5-4w43-2x63. 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-g6f5-4w43-2x63 in your dependencies?
O3 Security finds GHSA-g6f5-4w43-2x63 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.