← Back
CVE-2026-5076
critical
CVSS 9.8
Authentication Bypass in wordpress (CVE-2026-5076)
Summary
authentication bypass in wordpress (CVE-2026-5076). Successful exploitation can lead to full system takeover. Exploitable via ``arm_reset_password_key``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-5076** has been found in wordpress.
Attackers can target a specific entry point like ``arm_reset_password_key`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "wordpress CVE-2026-5076" on the vendor's site.
CVE-2026-5076 (wordpress) — CWE-287 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `arm_reset_password_key` / `wp_users.user_activation_key` / `wp_usermeta` / `armrp`
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
**authentication bypass** (CWE-287) exists in wordpress. Attackers reach the vulnerable code path via ``arm_reset_password_key`` without authentication.
📍 Affected scope
wordpress — . Attack surface: `arm_reset_password_key` / `wp_users.user_activation_key` / `wp_usermeta` / `armrp`.
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 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 request patterns matching this CVE's known IOCs. Run `grep -r 'wordpress' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'wordpress' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `wordpress` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- web https://codecanyon.net/item/armember-complete-wordpress-membership-system/17785056
- web https://www.wordfence.com/threat-intel/vulnerabilities/id/6b15eca5-fd47-4f8f-8ade-3a90e0bfc110?source=cve
- web https://nvd.nist.gov/vuln/detail/CVE-2026-5076
- web https://github.com/advisories/GHSA-53mc-7vx2-cm58