CVE-2026-63672 is a medium-severity (CVSS 6.1) Open Redirect vulnerability in egroupware/egroupware. A fix is available for egroupware/egroupware — see the affected versions and patch details below.
EGroupware: User-Controlled Identity Provider Selection in SAML Authentication
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-63672.
Real-World Exposure
egroupware/egroupware🐘egroupware/egroupwareReal-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
Summary
The login() function at line 130 passes the raw user-supplied value $_REQUEST['idp'] directly to SimpleSAMLphp's requireAuth() with only a regex check that the string starts with 'https://'. No validation is performed against a list of configured, trusted IdP entity IDs. An unauthenticated attacker can supply any HTTPS URL pointing to an IdP they control.
PoC
//api/src/Auth/Saml.php
function login()
{
// login (redirects to IdP)
$as = new SimpleSAML\Auth\Simple(self::$auth_source);
$as->requireAuth(preg_match('|^https://|', $_REQUEST['idp']) ?
['saml:idp' => $_REQUEST['idp']] : []);
Impact
An attacker can redirect authentication to a malicious IdP to capture credentials via phishing, or, if the SimpleSAMLphp configuration does not strictly validate IdP metadata, issue forged SAML assertions to authenticate as any user, including administrators.
Remediation
Validate the idp request parameter against a pre-configured whitelist of trusted IdP entity IDs stored in the application's SAML configuration. Reject and log any idp value not explicitly present in the trusted list before calling requireAuth().
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | egroupware/egroupware | all versions | 23.1.20260601composer require egroupware/egroupware:^23.1.20260601 |
| 🐘Packagist | egroupware/egroupware | ≥ 26.0.20251208&&< 26.6.20260616 | 26.6.20260616composer require egroupware/egroupware:^26.6.20260616 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for egroupware/egroupware, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update egroupware/egroupware to 23.1.20260601 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-63672 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.
Frequently Asked Questions
Is CVE-2026-63672 in your dependencies?
Find it across Packagist, including transitive dependencies.