🛡️ CVE-2026-66884 — oidcc-plug

⚪ Unknown ✅ No Known Exploit CWE-352 NVD
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Oidcc.Plug.AuthorizationCallback accepts callbacks with no authorize session or no state parameter, defeating CSRF protection

Summary

Cross-Site Request Forgery vulnerability in Erlang Ecosystem Foundation oidcc\_plug (Oidcc.Plug.AuthorizationCallback module) allows an attacker to make a victim's browser complete an authorization flow the victim never initiated.

This vulnerability is associated with program file lib/oidcc/plug/authorization\_callback.ex and program routine Oidcc.Plug.AuthorizationCallback.call/2.

A callback request that carries no Oidcc.Plug.Authorize session is processed with every security check disabled rather than being rejected. call/2 substitutes permissive defaults for the absent session, and each downstream check treats its value as nothing to compare and returns :ok, so the nonce, state, PKCE, peer IP and user agent checks are all skipped. A separate clause of check\_state/2 also accepts a state-less request when a verifier is present.

An attacker obtains an authorization code for their own provider account, then induces the victim to visit the callback endpoint with that code and no state parameter. The application signs the victim in as the attacker, so the victim's subsequent actions occur in the attacker's account where the attacker can read them. Applications reusing one callback for both signing in and linking a provider account are further exposed to account takeover, the attacker's account becoming linked to the victim's.

The permissive fallback serves no conforming flow. Third-party-initiated login reaches a relying party at a separate login initiation endpoint and causes it to send a fresh authentication request, and this library implements no such endpoint. Oidcc.Plug.Authorize always sends a state parameter, which an authorization server must echo, so no legitimate callback lacks one.

This issue affects oidcc\_plug: from 0.2.0-beta.1 before 0.5.0.

Workaround

Insert a plug before Oidcc.Plug.AuthorizationCallback that rejects the request when either the Oidcc.Plug.Authorize session or the state query parameter is missing. This restores the binding the callback fails to enforce and does not require modifying the library.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. A user must actively cooperate. Rated impact: confidentiality low, integrity low, availability none.

Weakness class

CVE-2026-66884 is classified as CWE-352: Cross-Site Request Forgery (CSRF). A state-changing request is accepted without proof it was intended, so another site can trigger it using the victim's session.

Affected software

CVE-2026-66884 is recorded against 2 packages.

  • oidcc-plug
  • unknown

Timeline and source

Published on 4 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

github.com (Advisory)
cna.erlef.org (Web)
github.com (Fix)
hex.pm (Package)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
CWE CWE-352
Public Exploit ✅ No
Source NVD
Published 2026-08-04
Updated 2026-08-12
Modified 2026-08-04

Affected Packages

Software From version Fixed in
oidcc-plug
unknown

Similar Threats

Free Vulnerability Check

Is your site affected by CVE-2026-66884?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2026-66884 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026