{"answers":{"affected":"2 open source packages ship an affected version, including getformwork/formwork. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27198 in the wild and no public exploit code.","fix":"Upgrade getformwork/formwork to 2.3.4 or later.","what":"CVE-2026-27198 is a high-severity vulnerability in getformwork formwork, published on 21 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-27198 and fix it if it is affected.\n\nWhat it is: CVE-2026-27198 is a high-severity vulnerability in getformwork formwork, published on 21 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-27198 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- getformwork/formwork (Packagist): affected from 2.0.0; fixed in 2.3.4\n- getformwork/formwork (Packagist): affected from 2.0.0; fixed in 2.3.4\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-27198/ (Markdown: https://insights.sbomify.com/CVE-2026-27198/index.md)","id":"CVE-2026-27198","markdown":"https://insights.sbomify.com/CVE-2026-27198/index.md","name":"CVE-2026-27198","record":{"aliases":["GHSA-34p4-7w83-35g2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Formwork CMS","requires_auth":"low_privilege","summary":"An authenticated editor can create admin accounts due to missing authorization checks, leading to full CMS compromise.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"formwork","vendor":"formwork_project"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Formwork is a flat file-based Content Management System (CMS). In versions 2.0.0 through 2.3.3, the application fails to properly enforce role-based authorization during account creation. Although the system validates that the specified role exists, it does not verify whether the current user has sufficient privileges to assign highly privileged roles such as admin. As a result, an authenticated user with the editor role can create a new account with administrative privileges, leading to full administrative access and complete compromise of the CMS. This issue has been fixed in version 2.3.4.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Formwork Improperly Manages Privileges During User Creation","id":"CVE-2026-27198","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Werkzeug safe_join() allows Windows special device names","id":"CVE-2026-27199"},"packages":[{"ecosystem":"Packagist","fixed":["2.3.4"],"introduced":["2.0.0"],"last_affected":[],"package":"getformwork/formwork","purl":null,"source":"GHSA-34p4-7w83-35g2"},{"ecosystem":"Packagist","fixed":["2.3.4"],"introduced":["2.0.0"],"last_affected":[],"package":"getformwork/formwork","purl":"pkg:composer/getformwork/formwork","source":"GHSA-34p4-7w83-35g2"}],"prev":{"headline":"Sentry: Improper Authentication on SAML SSO process allows user identity linking","id":"CVE-2026-27197"},"products":["formwork"],"published":"2026-02-21","related":[{"cvss_score":6.5,"headline":"Formwork CMS Has a Stored Cross-Site Scripting (XSS) Vulnerability in Blog Tags","id":"CVE-2025-65956","kev_date_added":null,"published":"2025-11-25"},{"cvss_score":4.8,"headline":"Formwork has a Cross-site scripting (XSS) vulnerability in Description metadata","id":"CVE-2024-37160","kev_date_added":null,"published":"2024-06-07"},{"cvss_score":4.8,"headline":"Formwork Cross-site Scripting (XSS) from Page title field","id":"CVE-2023-24230","kev_date_added":null,"published":"2023-02-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-24","vendors":["getformwork"]},"summary":"An authenticated editor can create admin accounts due to missing authorization checks, leading to full CMS compromise.","url":"https://insights.sbomify.com/CVE-2026-27198/"}