Nov 18, 2026·9 min read·2 visits
EGroupware's SAML authentication handler fails to validate the user-supplied 'idp' HTTP parameter against its configured list of trusted Identity Providers, only checking for an 'https://' prefix. This allows unauthenticated attackers to redirect users to rogue Identity Providers for credential phishing or potential session spoofing if SimpleSAMLphp metadata validation is loosely configured.
CVE-2026-63672 is an open redirect and insecure Identity Provider (IdP) selection vulnerability in the SAML Single Sign-On (SSO) authentication module of EGroupware. In affected versions, the login method in api/src/Auth/Saml.php accepts an unauthenticated HTTP request parameter (idp) and passes it to the underlying SimpleSAMLphp library after only verifying that the string begins with https://. Because the input is not validated against the application's configured whitelist of trusted identity providers, an attacker can construct a malicious link that redirects authenticating users to an arbitrary, attacker-controlled SAML Identity Provider.
EGroupware is an enterprise open-source groupware server written in PHP that supports multiple authentication backends, including Security Assertion Markup Language (SAML) 2.0 for Single Sign-On (SSO). The SAML integration is implemented within the EGroupware\Api\Auth\Saml class, located in api/src/Auth/Saml.php, which wraps an integrated instance of the SimpleSAMLphp library (SimpleSAML\Auth\Simple). This component exposes an unauthenticated attack surface during the initial stages of the authentication handshake when determining which Identity Provider (IdP) should authenticate the client.
In multi-IdP or federated environments, the Service Provider (SP) must determine the appropriate IdP for an incoming user session. EGroupware facilitates this by reading the idp parameter from the incoming HTTP request ($_REQUEST['idp']) inside its login() method. Once extracted, this parameter dictates the remote endpoint to which the user's browser is redirected for authentication.
CVE-2026-63672 (classified under CWE-601: URL Redirection to Untrusted Site) arises because EGroupware fails to verify that the user-supplied idp parameter corresponds to an administrator-configured, trusted Identity Provider. Instead, the application relies on a prefix check that merely confirms the string begins with https://.
Consequently, an unauthenticated attacker can supply an arbitrary HTTPS URL via the idp query parameter. When a victim interacts with a crafted EGroupware login URL, the server passes the untrusted URI directly to SimpleSAMLphp's requireAuth() routine, redirecting the user outside the organizational trust boundary to an attacker-controlled host.
The root cause of CVE-2026-63672 is the absence of allowlist validation on the $_REQUEST['idp'] parameter within EGroupware\Api\Auth\Saml::login() before passing control to the underlying SAML authentication library. While EGroupware maintains a server-level configuration property ($GLOBALS['egw_info']['server']['saml_idp']) that stores the list of authorized Identity Provider entity IDs or URLs, the vulnerable code path completely bypasses this configuration setting during login initiation.
Instead of comparing the incoming parameter against the configured allowlist, the developer implemented a regular expression check: preg_match('|^https://|', $_REQUEST['idp']). This regular expression evaluates whether the input string starts with the literal characters https://. Any arbitrary external domain using the HTTPS scheme satisfies this predicate.
When the regular expression evaluates to true (returns 1), the application constructs an options array ['saml:idp' => $_REQUEST['idp']] and passes it to SimpleSAML\Auth\Simple::requireAuth(). SimpleSAMLphp interprets the saml:idp key as an explicit directive to initiate an authentication request (AuthnRequest) with the specified IdP entity.
Because PHP's $_REQUEST superglobal aggregates inputs from $_GET, $_POST, and $_COOKIE, an attacker can inject the idp parameter via a standard GET query string. The vulnerability triggers immediately upon invocation of the SAML login routine without requiring any prior session state or authentication credentials.
In the vulnerable versions of EGroupware (< 23.1.20260601 and 26.0.20251208 to < 26.6.20260616), the login() method in api/src/Auth/Saml.php immediately instantiated the SimpleSAML\Auth\Simple object and passed the minimally checked $_REQUEST['idp'] parameter to requireAuth().
// api/src/Auth/Saml.php (Vulnerable implementation)
function login()
{
// login (redirects to IdP)
$as = new SimpleSAML\Auth\Simple(self::$auth_source);
// VULNERABLE: Only checks if the string starts with 'https://'
// Does not verify if $_REQUEST['idp'] is in the configured IdP allowlist
$as->requireAuth(preg_match('|^https://|', $_REQUEST['idp']) ?
['saml:idp' => $_REQUEST['idp']] : []);
// get attributes for (automatic) account creation
$attrs = $as->getAttributes();
if (!$attrs || empty($username = self::samlAttr(null, $attrs)))
{
throw new \Exception('Got NO '.(!$attrs ? 'attributes' : 'username attribute').' from SAML: '.json_encode($attrs));
}
// ... downstream account lookup and session creation ...
}In commits a87be9c177eaa9ac392f02fce45df833f638a7af and ec78ff4336d796fbe7803b0a4ab16e8388a1f81c, the maintainers remediated the vulnerability by introducing an explicit allowlist verification step at the entry point of the login() method.
diff --git a/api/src/Auth/Saml.php b/api/src/Auth/Saml.php
index 881fc36c1d3..0648df46266 100644
--- a/api/src/Auth/Saml.php
+++ b/api/src/Auth/Saml.php
@@ -125,6 +125,11 @@ function change_password($old_passwd, $new_passwd, $account_id=0)
*/
function login()
{
+ // check if one of the configured IdP's is requested, deny login if not
+ if (!in_array($_REQUEST['idp'], self::splitIdP($GLOBALS['egw_info']['server']['saml_idp'])))
+ {
+ return null;
+ }
// login (redirects to IdP)
$as = new SimpleSAML\Auth\Simple(self::$auth_source);
$as->requireAuth(preg_match('|^https://|', $_REQUEST['idp']) ?The patch calls self::splitIdP($GLOBALS['egw_info']['server']['saml_idp']), which parses the administrator-configured string of trusted IdP URIs (splitting on whitespace and newline characters via preg_split('/[\n\r ]+/', trim($config))) into an array. The in_array() function then checks if $_REQUEST['idp'] matches an entry in this array. If the parameter is not found in the allowlist, login() returns null immediately before instantiating SimpleSAML\Auth\Simple.
> [!NOTE]
> Fix Completeness Assessment: There are two minor implementation details in the patch worth noting. First, in_array() is called without the $strict = true argument, relying on PHP's loose comparison; however, because splitIdP() returns an array of strings, type juggling risks are minimalunless non-scalar array inputs are passed via $_REQUEST['idp']. Second, because the in_array() check runs unconditionally at the start of login(), any call to login() where $_REQUEST['idp'] is unset or empty will fail the check (returning null) unless the empty value matches an empty string element returned by splitIdP(). For standard multi-IdP selection flows where $_REQUEST['idp'] is explicitly populated by the login UI, the patch effectively neutralizes arbitrary IdP injection.
Exploiting CVE-2026-63672 requires no authentication or privileges on the target EGroupware server. The primary prerequisite is that the target EGroupware instance has SAML authentication enabled and reachable by the victim. Because the attack relies on redirecting a user's browser session or processing an assertion within the user's browser context, user interaction (UI:R) is required.
In a credential harvesting scenario, the attacker sets up a rogue HTTPS server hosting a counterfeit SSO login portal designed to mimic the target organization's legitimate Identity Provider (e.g., Okta, Azure AD, or Keycloak). The attacker then crafts a URL pointing to the legitimate EGroupware server's SAML login handler with the idp parameter set to the attacker's domain:
GET /egroupware/index.php?auth=saml&idp=https%3A%2F%2Fidp.attacker-controlled.example%2Fsaml2%2Fidp%2FSSOService.php HTTP/1.1
Host: egroupware.target-enterprise.orgWhen the victim clicks this link, the request is processed by the legitimate egroupware.target-enterprise.org server. Because the initial domain in the link belongs to the trusted enterprise groupware server, standard user scrutiny and email gateway link reputation checks may not flag the URL as malicious. Once the request reaches Saml::login(), the user is redirected to https://idp.attacker-controlled.example/... where their credentials can be captured.
A secondary, higher-impact exploitation path involves SAML assertion forgery and account impersonation. After redirecting the victim to the rogue IdP, the attacker's server can generate and sign a SAML Response containing an assertion for an arbitrary user account (such as an administrative username) and send it back to EGroupware's Assertion Consumer Service (ACS) endpoint. In standard SimpleSAMLphp deployments, the SP checks the Issuer entity ID against static local metadata (metadata/saml20-idp-remote.php) and verifies the cryptographic signature against a pinned certificate. However, if the SimpleSAMLphp instance is configured to allow dynamic metadata retrieval from untrusted entity IDs or lacks strict certificate pinning in a loose federation setup, SimpleSAMLphp will accept the rogue assertion.
If the assertion is accepted by SimpleSAMLphp, control returns to Saml::login() in EGroupware:
$attrs = $as->getAttributes();
$username = self::samlAttr(null, $attrs);
// Checks if user exists or auto-creates account
if (!$GLOBALS['egw']->accounts->name2id($username, 'account_lid', 'u')) { ... }
// Creates authenticated EGroupware session
return $GLOBALS['egw']->session->create($username, null, null, false, false);Under such misconfigurations, EGroupware extracts the attacker-supplied username attribute from $as->getAttributes() and invokes $GLOBALS['egw']->session->create(), granting an authenticated session as the target user.
The vulnerability is scored at CVSS v3.1 6.1 (Medium) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. The Scope is marked as Changed (S:C) because the vulnerability located within the EGroupware Service Provider context redirects the user and shifts the authentication trust boundary to an external, third-party domain.
The primary confidentiality impact (C:L) stems from the facilitation of high-credibility spearphishing campaigns. Because the attack initiates from the authentic EGroupware domain and utilizes the application's actual SAML redirection workflow, victims are directed seamlessly to the attacker's login form. If users enter their SSO credentials on the rogue IdP, the attacker compromises their enterprise identity, which often grants access to multiple federated applications beyond EGroupware.
The integrity impact (I:L) reflects the ability to manipulate the authentication flow and, in environments with permissive SimpleSAMLphp metadata configurations, inject forged SAML assertions to establish unauthorized sessions or trigger automatic account provisioning (auto-create functionality in Saml.php). There is no direct impact on system availability (A:N).
From a threat intelligence perspective, CVE-2026-63672 currently exhibits an EPSS score of 0.002 (0.20%, 9.86th percentile), indicating a low probability of widespread automated exploitation in the immediate term. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploit code or automated Nuclei templates have been published as of the advisory release.
Organizations running EGroupware with SAML authentication enabled should upgrade to the patched maintenance releases that enforce strict allowlist validation against $GLOBALS['egw_info']['server']['saml_idp']. Specifically, installations on the 23.1 branch must upgrade to version 23.1.20260601 or later, and installations on the 26.x branch must upgrade to version 26.6.20260616 or later.
For environments where an immediate software upgrade is not feasible, administrators can apply the patch manually to api/src/Auth/Saml.php by inserting the in_array($_REQUEST['idp'], self::splitIdP($GLOBALS['egw_info']['server']['saml_idp'])) validation check at the beginning of the login() function.
Alternatively, administrators can deploy a compensating control at the reverse proxy (Nginx, Apache) or Web Application Firewall (WAF) layer. The proxy should inspect incoming HTTP GET and POST requests for the idp parameter and block any request where the parameter value does not strictly match the organization's known, authorized Identity Provider entity URI.
Finally, administrators should audit their underlying SimpleSAMLphp configuration (metadata/saml20-idp-remote.php and config/config.php) to ensure defense-in-depth. Verify that dynamic metadata loading (metarefresh from untrusted sources) is disabled and that all configured Identity Providers have explicitly pinned X.509 certificates for assertion signature verification.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N| Product | Affected Versions | Fixed Version |
|---|---|---|
egroupware EGroupware | < 23.1.20260601 | 23.1.20260601 |
egroupware EGroupware | >= 26.0.20251208, < 26.6.20260616 | 26.6.20260616 |
| Attribute | Detail |
|---|---|
| CVE ID | CVE-2026-63672 (GHSA-pr4x-6fj4-gm4h) |
| Weakness Class | CWE-601: URL Redirection to Untrusted Site ('Open Redirect') |
| Affected Component | EGroupware\Api\Auth\Saml::login() (api/src/Auth/Saml.php) |
| Attack Vector | Network (Unauthenticated HTTP GET/POST parameter 'idp') |
| CVSS v3.1 Score | 6.1 Medium (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) |
| EPSS Score | 0.20% (9.86th percentile) |
| Primary Impact | Redirection to untrusted SAML Identity Provider / Credential Phishing |
| CISA KEV Status | Not Listed |
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.
CVE-2026-62336 (GHSA-xhv5-8fpq-g7hf) is a high-severity local privilege escalation, arbitrary file overwrite, and denial-of-service vulnerability in qbee-agent, the client daemon for the qbee.io IoT device management platform. Prior to version 2026.27, the root-privileged agent failed to validate path components against symbolic links during directory creation and file opening operations in app/configuration/file_manager.go. Local unprivileged users can exploit this flaw by planting symlinks in user-controlled configuration paths or predictable temporary staging locations, causing the daemon to overwrite, truncate, or change ownership of sensitive root-owned system files.
CVE-2026-110782 is an authentication bypass and cryptographic signature verification failure in the SimpleSAMLphp SAML2 library (simplesamlphp/saml2). Resulting from an incomplete fix for CVE-2026-49283, the HTTP-Artifact binding implementation verifies the outer ArtifactResponse signature but unconditionally returns unsigned embedded SAML Responses without verifying signatures or validating that the embedded issuer matches the artifact issuer. In multi-IdP federation environments, an attacker controlling one trusted Identity Provider (IdP) can forge arbitrary identity assertions claiming to originate from another trusted IdP.
CVE-2026-110789 (GHSA-rvfr-cqwq-rc4j) is a high-severity pre-authentication Denial of Service (DoS) vulnerability in the @libp2p/crypto package of the js-libp2p networking stack prior to version 5.1.22. An improper length validation flaw in the ASN.1 DER decoder allows an unauthenticated remote peer to send a crafted RSA public key during the Identify protocol exchange, forcing the parser into a synchronous loop over attacker-claimed length values. Because this loop executes within a single Node.js event-loop tick prior to identity or cryptographic signature verification, it bypasses application timeouts, stalls the event loop for 4 to 5 seconds per connection, and transiently allocates up to 2 GB of memory.
CVE-2026-119793 (GHSA-x2vm-cf3p-m2w8) is a resource consumption vulnerability in the @libp2p/gossipsub module of the js-libp2p ecosystem. Prior to @libp2p/gossipsub version 17.0.0 and js-libp2p version 3.3.9, the GossipSub implementation processed incoming subscription RPC messages without enforcing per-peer or global limits on the number or cumulative byte size of subscribed topics in its default configuration. An unauthenticated remote peer can exploit this flaw by streaming continuous batches of unique topic subscription strings over an established connection, causing unbounded growth of the internal topics Map. This leads to V8 heap exhaustion (Out-Of-Memory crash) and severe CPU starvation on the main event loop during peer disconnection teardown.
Filament Curator, a media picker plugin for Filament panels in Laravel applications, contains a Stored Cross-Site Scripting (XSS) vulnerability in versions prior to 3.7.9, 4.1.2, and 5.1.2. The application accepts image/svg+xml uploads by default and stores them on disk without stripping executable XML markup. When a panel user opens an uploaded SVG via the View action, the file renders as a top-level document in the browser, executing embedded JavaScript within the origin of the Filament application.
CVE-2026-63182 is a high-severity XML Signature Wrapping (XSW) vulnerability in LightSAML (litesaml/lightsaml), a PHP library implementing SAML 2.0 data models and cryptographic verification. An architectural discrepancy between how LightSAML deserializes direct child assertions and how the underlying robrichards/xmlseclibs library resolves XML document fragment identifiers allows an attacker with a valid signed assertion to forge arbitrary SAML identity claims and bypass authentication.