What's new?
This is a security hardening release. We recommend that everyone updates.
Security hardening.
As part of our commitment to security, this release addresses issues which could potentially have security
repercussions under specific circumstances even though we cannot find a practical way to exploit them. Most of these
have to do with the Login with Apple improvements described below, stricter rules about who can unlink
social logins from other users' accounts, and logging. You can consult the CHANGELOG for the full list of issues
addressed.
Spotify integration removed.
Spotify discontinued the API login program this plugin relied on, so the Login with Spotify plugin has been removed. If you had it installed, Joomla will uninstall it as part of this update. You will see the message “Uninstalling the plugin PLG_SOCIALLOGIN_SPOTIFY was successful” when installing the new version confirming that. Users who only logged in through Spotify will need another way to log in, e.g. the password reset feature.
"Remember me" is now optional.
Social logins used to always create a persistent "remember me" login. You can now turn this off in the System -
Social Login plugin options.
Login with Apple improvements.
The bundled phpseclib library was updated to version 3, and the signed login response is validated more
strictly.
Changelog
New features
- Social logins no longer force "remember me"; it can now be disabled in the system plugin's options
Removed features
- Removed the Spotify integration (its API login program was discontinued)
Bug fixes
- [HIGH] Social login could be tricked into linking an attacker's account to a logged-in user
- [LOW] Database writes for social login data now use bound query parameters throughout
- [LOW] Debug output of OAuth error details is now escaped before display
- [LOW] Debug-mode OAuth error details no longer show literal HTML tags
- [LOW] German and Italian language files: fixed unescaped double quotes that broke strict INI parsing
- [LOW] Linking Google from the backend failed on servers whose firewall blocks ".profile" in request parameters
- [LOW] Login error logs no longer record user email addresses on production sites
- [LOW] Login with Microsoft: invalid custom tenant IDs can no longer alter the login endpoint
- [LOW] Saving your profile can no longer be abused to forge social login link data
- [LOW] Social link buttons now escape all attribute values in their default layout
- [LOW] Social login error messages shown to visitors are now HTML-escaped
- [LOW] The "Backend only" choice of the Enabled Applications option could not be saved in any social login plugin [gh-150]
- [LOW] Unlinking a social account no longer exposes the session token in the page address
- [MEDIUM] Debug logging no longer writes users' social network access tokens to the log file
- [MEDIUM] Failed social logins now show a generic error unless the site's debug mode is on
- [MEDIUM] Login with Apple: a temporary connection problem can no longer bypass the signature check
- [MEDIUM] Login with Apple: the login response is now bound to each individual login attempt
- [MEDIUM] Login with Apple: tighter validation of the signed login response
- [MEDIUM] Login with Apple: tokens are no longer written to the log file on validation failures
- [MEDIUM] The "don't remind me" action now requires a confirmed form submission
- [MEDIUM] Unlinking someone else's social login now requires Super User privileges
Miscellaneous changes
- Login with Apple: updated the bundled phpseclib library to version 3
- Login with Facebook now uses HTTPS for the initial authorization redirect
- PHP 8.4 compatibility: fixed a "Creation of dynamic property" deprecation during installation of the system plugin
- PHP 8.4 compatibility: fixed an "Implicitly marking parameter as nullable" deprecation in Login with Apple
- Plugin packages now consistently include index.html directory guards
- Smaller plugin package: removed unused third-party SSH/SFTP library code
- Social login profile lookups now escape wildcard characters in their match patterns