Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-110106 medium CVSS 4.2

Vulnerability in RuoYi-Vue-Plus (CVE-2026-110106)

Summary

Vulnerability in RuoYi-Vue-Plus (CVE-2026-110106). Risk of unauthorized operations or information disclosure. Exploitable via DELETE /auth/unlock/{socialId}.

Original description

The description as published by the source.

RuoYi-Vue-Plus through 6.0.0 contains an insecure direct object reference vulnerability that allows authenticated users to delete other users' social login bindings by supplying their socialId. Attackers can send DELETE /auth/unlock/{socialId} requests with a victim's binding id to remove their GitHub, WeChat, or Gitee binding and stored OAuth tokens, blocking social login.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-110106 has been found in RuoYi-Vue-Plus.
Attackers can target a specific entry point like DELETE /auth/unlock/{socialId} over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "RuoYi-Vue-Plus CVE-2026-110106" on the vendor's site.

CVE-2026-110106 (RuoYi-Vue-Plus) — CWE-639 / CVSS v3 4.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DELETE /auth/unlock/{socialId}
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-639) exists in RuoYi-Vue-Plus. Attackers reach the vulnerable code path via DELETE /auth/unlock/{socialId}.

📍 Affected scope

Check the vendor advisory for the affected versions of RuoYi-Vue-Plus. Attack surface: DELETE /auth/unlock/{socialId}.

🔥 Severity

Severity: Medium (CVSS 4.2/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual DELETE /auth/unlock/{socialId} requests with malformed payloads or SQL meta-characters. Run grep -r 'RuoYi-Vue-Plus' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'RuoYi-Vue-Plus' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で RuoYi-Vue-Plus を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'DELETE /auth/unlock/{socialId}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで DELETE /auth/unlock/{socialId} への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against DELETE /auth/unlock/{socialId} on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details