Skip to main content

Dancer2-Plugin-Auth-OAuth EUVDEUVD-2026-41686

| CVE-2026-12746 HIGH
Cross-Site Request Forgery (CSRF) (CWE-352)
8.1
CVSS 3.1 · Vendor
Share

Severity by source

Vendor (CNA) PRIMARY
8.1 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
vuln.today AI
9.3 CRITICAL

Network-delivered, no attacker privileges required (PR:N), but victim must visit crafted URL (UI:R); account takeover crosses scope boundary (S:C) with full confidentiality and integrity loss, no availability impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (CNA).

CVSS VectorVendor

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

2
Patch available
Jul 04, 2026 - 19:01 EUVD
Analysis Generated
Jul 04, 2026 - 18:18 vuln.today

Description PRE-NVD

Disclosed via oss-security. NVD scoring and full description are pending.

AnalysisAI

Login CSRF via a missing OAuth 2.0 state parameter in Dancer2::Plugin::Auth::OAuth::Provider (all versions before 0.23) allows a remote, unauthenticated attacker to associate their own OAuth provider identity and access token with a victim's application session, potentially achieving persistent account takeover. The plugin's authentication_url method never generates a state value, and the callback handler never validates one, leaving the entire authorization flow unbound to the session that initiated it. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Attacker authenticates OAuth flow using own provider account
Delivery
Captures authorization callback URL with attacker's authorization code
Exploit
Crafts delivery mechanism (phishing link, malicious page)
Execution
Victim's browser executes callback URL against vulnerable application
Persist
Plugin registers attacker's OAuth token to victim's active session
Impact
Attacker logs into victim's account using own provider credentials

Vulnerability AssessmentAI

Exploitation The target application must be running Dancer2::Plugin::Auth::OAuth::Provider at a version before 0.23 and must use it as an OAuth 2.0 login or account-linking mechanism. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment No CVSS vector was supplied by the advisory or NVD for this CVE, so all metric assessments are independently derived from the description. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker initiates a legitimate OAuth 2.0 authorization flow against the target Dancer2 application using their own provider account, capturing the resulting callback URL that contains the authorization code. The attacker then delivers this callback URL to a victim via phishing or a crafted web page, causing the victim's browser to visit it while holding an active application session. …
Remediation Upgrade Dancer2-Plugin-Auth-OAuth to version 0.23 or later via CPAN (cpanm Dancer2::Plugin::Auth::OAuth or cpan Dancer2-Plugin-Auth-OAuth). … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours: Identify all applications using Dancer2::Plugin::Auth::OAuth::Provider and assess which are accessible from the internet. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

EUVD-2026-41686 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy