/

CVE-2026-122019

Severity:

HIGH RISK

(7.3)

Authorization Bypass (CWE-639) in 6valley Social Login

CVE-2026-122019

Deferred

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-285, CWE-639

Impact:

Authorization Bypass

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A remotely reachable flaw in 6valley's social login flow may allow authorization checks to be bypassed by manipulating the user_response argument. The risk depends on how the existing-account check handles that input, and a public exploit has been reported.

Affected context

The issue is reported in 6amTech 6valley 16.0, in the Social Login Flow endpoint /api/v1/auth/existing-account-check and its existingAccountCheck function. It may arise when the endpoint uses the supplied user_response to make account or access decisions without adequately verifying that the input is trustworthy and correctly associated with the user.

Exploit preconditions

  • Attack surface: The remotely reachable existing-account-check endpoint
  • Required access: The description does not specify whether authentication or other access is required
  • Trigger point: Processing of the user_response argument in the social login flow
  • Why exploitation may be possible: Manipulating this argument may affect authorization decisions if its contents are not adequately validated or bound to a trusted identity

Why this happens

The reported behavior is consistent with authorization decisions relying on user-controlled input. This maps most specifically to CWE-639: Authorization Bypass Through User-Controlled Key and is also associated with CWE-285: Improper Authorization. Abstractly, the insecure pattern occurs when input can influence which account or authorization context is accepted without sufficient validation and access-control checks.

Potential impact

  • An attacker may bypass an authorization check in the social login flow
  • Affected account or application functionality could be accessed without the intended authorization
  • Depending on the surrounding account-binding logic, account access or identity association could be affected

General mitigation guidance

Defensive approaches generally focus on keeping authorization decisions independent of untrusted request fields:

  • Derive identity and account context from trusted, verified authentication results
  • Validate social login responses and bind them to the expected provider, user, and login transaction
  • Apply server-side authorization checks for every sensitive operation
  • Minimize trust in client-supplied identifiers and response attributes
  • Limit application privileges and access to sensitive account functions

How teams detect issues like this

Review social login handlers for authorization or account-selection decisions based on request-controlled fields such as user_response. Use static analysis and code review to identify missing validation, identity binding, or server-side authorization checks. Enforce policies requiring trusted authentication claims and explicit authorization before sensitive account actions, and monitor for unusual requests to the existing-account-check endpoint.

Sources

SourceLink
github.comgithub.com/oscar2744/CVE-Submit/issues/3
vuldb.comvuldb.com/cve/CVE-2026-122019
vuldb.comvuldb.com/submit/1024992
vuldb.comvuldb.com/vuln/431085
vuldb.comvuldb.com/vuln/431085/cti

Frequently asked

questions

The report identifies a remotely launchable attack involving the existing-account-check endpoint. The exact exposure depends on deployment and endpoint access controls.

The available description does not specify an authentication requirement. Whether access is needed should be assessed against the deployed social login flow.

Base account and authorization decisions on verified identity information, validate and bind social login responses to the expected flow, and enforce authorization on the server.

Treat request-supplied identity and response fields as untrusted, require explicit server-side authorization checks, and include social login flows in security reviews and automated testing.

Find out what's already
exploitable in your codebase.