{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44224 exists.","fix":"No fix has been published for CVE-2026-44224 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44224 is a high-severity vulnerability in requarks wiki, published on 12 May 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44224 and fix it if it is affected.\n\nWhat it is: CVE-2026-44224 is a high-severity vulnerability in requarks wiki, published on 12 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44224 exists.\n\nAffected product: requarks wiki. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44224/ (Markdown: https://insights.sbomify.com/CVE-2026-44224/index.md)","id":"CVE-2026-44224","markdown":"https://insights.sbomify.com/CVE-2026-44224/index.md","name":"CVE-2026-44224","record":{"aliases":["GHSA-cq3g-mwrg-v2rv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Wiki.js","requires_auth":"high_privilege","summary":"A user with manage:users permission can self-assign to the Administrators group via the users.update mutation, gaining full site administrator access.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wiki.js","vendor":"requarks"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Wiki.js: Privilege Escalation via Missing Group Validation in users.update","id":"CVE-2026-44224","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Pulpy: Incomplete filesystem sandbox in pulpy.fs bridge allows packaged web apps to read arbitrary user files","id":"CVE-2026-44225"},"packages":[],"prev":{"headline":"vLLM: extract_hidden_states speculative decoding crashes server on any request with penalty parameters","id":"CVE-2026-44223"},"products":["wiki"],"published":"2026-05-12","related":[{"cvss_score":9.1,"headline":"Security feature bypass in n/a","id":"CVE-2025-56643","kev_date_added":null,"published":"2025-11-18"},{"cvss_score":8.6,"headline":"Directory Traversal in Wiki.js","id":"CVE-2020-15236","kev_date_added":null,"published":"2020-10-05"},{"cvss_score":8.2,"headline":"Stored XSS via SVG in Requarks/wiki","id":"CVE-2021-43855","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":8.2,"headline":"Stored XSS in non-image uploads in Requarks/wiki","id":"CVE-2021-43856","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":8.1,"headline":"Improper write access check in Requarks/wiki","id":"CVE-2022-23654","kev_date_added":null,"published":"2022-02-22"},{"cvss_score":7.6,"headline":"XSS in Wiki.js","id":"CVE-2021-21383","kev_date_added":null,"published":"2021-03-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-13","vendors":["requarks"]},"summary":"A user with manage:users permission can self-assign to the Administrators group via the users.update mutation, gaining full site administrator access.","url":"https://insights.sbomify.com/CVE-2026-44224/"}