CVE-2026-41671: Admidio OIDC Token Introspection Endpoint Returns Vulnerability
MODERATECVE-2026-41671 is a MODERATE (CVSS 6.8) oidc token introspection endpoint returns vulnerability (CWE-287: Improper Authentication) affecting Admidio libraries in the Packagist ecosystem. The issue involves oidc token introspection endpoint returns active for all tokens without validation. Remediation is available by upgrading affected packages to version 5.0.9.
CVE-2026-41671 at a Glance
Security Impact
CVSS: 6.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N).
How to Fix CVE-2026-41671
To remediate this vulnerability, upgrade all affected Admidio dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade admidio/admidio to 5.0.9
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for admidio/admidio
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-41671, inspect your project dependencies for Admidio:
inspect dependencies for admidio/admidio
Analyze the terminal output to locate any version of Admidio in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.0.9), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In Admidio, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-41671 Affected Admidio Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
admidio/admidio
|
Packagist |
< 5.0.9
|
5.0.9
|
References
Frequently Asked Questions
What is CVE-2026-41671?
Which Admidio versions are affected?
What version fixes CVE-2026-41671?
Is admidio/admidio affected?
What is the CVSS score of CVE-2026-41671?
What CWE is associated with CVE-2026-41671?
How can I check Packagist dependencies for CVE-2026-41671?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9xx5-cv6j-x533",
"modified" : "2026-05-08T20:14:32Z",
"published" : "2026-04-29T21:58:56Z",
"aliases" : [ "CVE-2026-41671" ],
"summary" : "Admidio: OIDC Token Introspection Endpoint Returns Active for All Tokens Without Validation",
"details" : "## Summary\n\nThe OIDC token introspection endpoint (`/modules/sso/index.php/oidc/introspect`) always returns `{\"active\": true}` for every request, regardless of whether a valid token is provided, whether the token is expired, revoked, or completely fabricated. The endpoint performs no authentication of the calling resource server and no validation of the submitted token. Any resource server that relies on this introspection endpoint to validate access tokens will accept all requests as authorized, enabling complete authentication bypass.\n\nAdditionally, the OIDC token revocation endpoint (`/oidc/revoke`) returns `{\"revoked\": true}` without actually revoking any token, preventing resource servers from invalidating compromised credentials.\n\n## Details\n\nThe vulnerability is in `src/SSO/Service/OIDCService.php`, lines 604-619:\n\n```php\npublic function handleIntrospectionRequest() {\n // TODO_RK\n if (!$this->isServiceSetup) {\n $this->setupService();\n }\n return new JsonResponse([\"active\" => true]);\n}\n\npublic function handleRevocationRequest() {\n // TODO_RK\n if (!$this->isServiceSetup) {\n $this->setupService();\n }\n\n return new JsonResponse([\"revoked\" => true]);\n}\n```\n\nThe introspection endpoint is routed at `modules/sso/index.php`, line 58-59:\n\n```php\n} elseif (strpos($requestUri, '/oidc/introspect') !== false) {\n $response = $oidcService->handleIntrospectionRequest();\n```\n\nThe router comment at line 35 says \"Login checks will be done in the individual endpoint handler functions!\" but neither `handleIntrospectionRequest` nor `handleRevocationRequest` perform any authentication or authorization checks.\n\nPer RFC 7662 (OAuth 2.0 Token Introspection), the introspection endpoint:\n1. MUST authenticate the calling resource server (Section 2.1)\n2. MUST validate the submitted token against its database\n3. MUST return `{\"active\": false}` for invalid, expired, or revoked tokens\n\nThe current implementation violates all three requirements.\n\n**Attack flow:**\n1. Attacker obtains a resource server's endpoint URL that uses Admidio as its OIDC provider\n2. Attacker crafts any arbitrary string as a Bearer token\n3. Resource server sends the fabricated token to `/oidc/introspect` for validation\n4. Admidio returns `{\"active\": true}` without any checks\n5. Resource server accepts the fabricated token as valid and grants access\n\n**The revocation bypass compounds this:** If a legitimate token is stolen, the resource server or client application cannot revoke it. Calling `/oidc/revoke` returns success without actually revoking the token in the database, so the stolen token remains usable indefinitely (until its expiry time).\n\n## PoC\n\n```bash\n# Step 1: Confirm the introspection endpoint exists and always returns active\n# No valid token needed - any string works\ncurl -X POST https://TARGET/modules/sso/index.php/oidc/introspect \\\n -d \"token=COMPLETELY_FABRICATED_TOKEN_12345\"\n\n# Expected response: {\"active\":true}\n\n# Step 2: Try with an empty token\ncurl -X POST https://TARGET/modules/sso/index.php/oidc/introspect \\\n -d \"token=\"\n\n# Expected response: {\"active\":true}\n\n# Step 3: Demonstrate that revocation is also broken\ncurl -X POST https://TARGET/modules/sso/index.php/oidc/revoke \\\n -d \"token=any_valid_token_here\"\n\n# Expected response: {\"revoked\":true}\n# But the token is NOT actually revoked in the database\n\n# Step 4: Verify the token is still active after \"revocation\"\ncurl -X POST https://TARGET/modules/sso/index.php/oidc/introspect \\\n -d \"token=any_valid_token_here\"\n\n# Still returns: {\"active\":true}\n```\n\n## Impact\n\n- **Authentication Bypass on Resource Servers**: Any application (wiki, CMS, project management tool, etc.) configured to validate tokens against this Admidio OIDC introspection endpoint will accept completely fabricated tokens. An attacker can impersonate any user on all connected resource servers.\n- **Inability to Revoke Compromised Tokens**: If a legitimate access token is leaked or stolen, there is no way to revoke it through the standard OIDC revocation flow. The token remains valid until its 1-hour expiry.\n- **Scope Change (S:C)**: The vulnerability in the Admidio authorization server directly impacts the security of all connected resource servers (different security authority), which is why the CVSS scope is Changed.\n\n## Recommended Fix\n\nReplace the stub implementations with proper token introspection and revocation logic:\n\n```php\npublic function handleIntrospectionRequest() {\n if (!$this->isServiceSetup) {\n $this->setupService();\n }\n \n $request = $this->getRequest();\n \n // 1. Authenticate the resource server (RFC 7662 Section 2.1)\n // The resource server MUST authenticate using client credentials\n $clientId = $request->getParsedBody()['client_id'] ?? null;\n $clientSecret = $request->getParsedBody()['client_secret'] ?? null;\n \n if (!$clientId || !$this->clientRepository->validateClient($clientId, $clientSecret, null)) {\n return new JsonResponse(['error' => 'invalid_client'], 401);\n }\n \n // 2. Get and validate the token\n $tokenValue = $request->getParsedBody()['token'] ?? '';\n if (empty($tokenValue)) {\n return new JsonResponse(['active' => false]);\n }\n \n try {\n // Validate the token using the resource server\n $validatedRequest = $this->resourceServer->validateAuthenticatedRequest(\n $request->withHeader('Authorization', 'Bearer ' . $tokenValue)\n );\n \n $tokenId = $validatedRequest->getAttribute('oauth_access_token_id');\n \n // Check if token is revoked\n if ($this->accessTokenRepository->isAccessTokenRevoked($tokenId)) {\n return new JsonResponse(['active' => false]);\n }\n \n $token = $this->accessTokenRepository->getToken($tokenId);\n \n // Check expiry\n if ($token->getExpiryDateTime() < new \\DateTimeImmutable()) {\n return new JsonResponse(['active' => false]);\n }\n \n return new JsonResponse([\n 'active' => true,\n 'sub' => $token->getUserIdentifier(),\n 'client_id' => $token->getClient()->getIdentifier(),\n 'exp' => $token->getExpiryDateTime()->getTimestamp(),\n 'scope' => implode(' ', array_map(fn($s) => $s->getIdentifier(), $token->getScopes())),\n ]);\n } catch (\\Exception $e) {\n return new JsonResponse(['active' => false]);\n }\n}\n\npublic function handleRevocationRequest() {\n if (!$this->isServiceSetup) {\n $this->setupService();\n }\n \n $request = $this->getRequest();\n \n // Authenticate the client\n $clientId = $request->getParsedBody()['client_id'] ?? null;\n $clientSecret = $request->getParsedBody()['client_secret'] ?? null;\n \n if (!$clientId || !$this->clientRepository->validateClient($clientId, $clientSecret, null)) {\n return new JsonResponse(['error' => 'invalid_client'], 401);\n }\n \n $tokenValue = $request->getParsedBody()['token'] ?? '';\n if (!empty($tokenValue)) {\n try {\n $validatedRequest = $this->resourceServer->validateAuthenticatedRequest(\n $request->withHeader('Authorization', 'Bearer ' . $tokenValue)\n );\n $tokenId = $validatedRequest->getAttribute('oauth_access_token_id');\n $this->accessTokenRepository->revokeAccessToken($tokenId);\n } catch (\\Exception $e) {\n // RFC 7009: The server responds with HTTP 200 even for invalid tokens\n }\n }\n \n return new JsonResponse([], 200);\n}\n```",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "admidio/admidio"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "5.0.9"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 5.0.8"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/Admidio/admidio/security/advisories/GHSA-9xx5-cv6j-x533"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-41671"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/Admidio/admidio"
}, {
"type" : "WEB",
"url" : "https://github.com/Admidio/admidio/releases/tag/v5.0.9"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-287" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-29T21:58:56Z",
"nvd_published_at" : "2026-05-07T04:16:32Z"
}
}