Privilege Escalation in Requarks (CVE-2026-44224)
Summary
Vulnerability in Requarks (CVE-2026-44224). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.5.313 or later.
Original description
The description as published by the source.
Wiki.js is an open source wiki app built on Node.js. Prior to 2.5.313, the users.update GraphQL mutation accepts an arbitrary groups array and applies it directly to the database with no validation of the group IDs supplied. The resolver passes the caller's arguments straight to the model without any ownership check or restriction on which groups can be assigned. A user with manage:users — a permission typically delegated to wiki moderators for account management — can set groups:[1] on their own account to self-assign to the Administrators group. After re-authentication, the fresh JWT carries manage:system, granting full site administrator access in a single mutation call. This vulnerability is fixed in 2.5.313.
Source: NIST National Vulnerability Database 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-44224 has been found in Requarks.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade Requarks to 2.5.313 or later.
If unsure, ask your IT team or search "Requarks CVE-2026-44224" on the vendor's site.
CVE-2026-44224 (Requarks) — CWE-269 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.5.313 — apply immediately
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.
A vulnerability (CWE-269) exists in Requarks.
Check the vendor advisory for the affected versions of Requarks.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2.5.313.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Requarks' . 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
-
1Identify exposure identify
grep -r 'Requarks' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Requarksを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Requarks to 2.5.313ステージング環境で 2.5.313 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov