Authentication bypass via unconditional token activation
Published May 7, 2026 · Updated May 7, 2026
Authentication bypass in Admidio before 5.0.9 allows remote attackers to authorize fabricated tokens through OIDC introspection. OIDCService.php's handleIntrospectionRequest returns active true without authenticating the caller or validating, expiry-checking, or revocation-checking the submitted token. Exploitation requires a connected resource server to rely on this endpoint, which then treats the fabricated token as valid and grants access under the associated authorization flow.
Summary
What happened
Authentication bypass in Admidio before 5.0.9 allows remote attackers to authorize fabricated tokens through OIDC introspection. OIDCService.php's handleIntrospectionRequest returns active true without authenticating the caller or validating, expiry-checking, or revocation-checking the submitted token. Exploitation requires a connected resource server to rely on this endpoint, which then treats the fabricated token as valid and grants access under the associated authorization flow.
The record
- CVE
- CVE-2026-41671
- Published
- May 7, 2026
- Updated
- May 7, 2026
- Vendor
- Admidio
- Product
- Admidio
- Classifications
- CWE-287, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 7, 2026CVE publishedPublication date reported by the CVE source.
- May 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.0.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GHSA fabricated-token curl proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo