Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-27198: CWE-269: Improper Privilege Management in getformwork formwork

0
High
VulnerabilityCVE-2026-27198cvecve-2026-27198cwe-269
Published: Sat Feb 21 2026 (02/21/2026, 05:11:42 UTC)
Source: CVE Database V5
Vendor/Project: getformwork
Product: formwork

Description

CVE-2026-27198 is a high-severity vulnerability in the getformwork CMS versions 2. 0. 0 through 2. 3. 3. It arises from improper privilege management where the system fails to verify if an authenticated user with editor role has the right to assign highly privileged roles like admin during account creation. This allows an editor-level user to create new accounts with administrative privileges, leading to full CMS compromise. The vulnerability requires authentication but no user interaction beyond normal use. It impacts confidentiality, integrity, and availability severely. The issue is fixed in version 2.

AI-Powered Analysis

AILast updated: 02/21/2026, 20:49:48 UTC

Technical Analysis

The vulnerability identified as CVE-2026-27198 affects the getformwork flat file-based CMS in versions 2.0.0 through 2.3.3. The root cause is improper enforcement of role-based authorization during account creation. While the system validates that the role specified for a new account exists, it does not check whether the user creating the account has sufficient privileges to assign that role. Specifically, an authenticated user with the editor role can create new accounts with administrative privileges, bypassing intended access controls. This flaw is categorized under CWE-269 (Improper Privilege Management). Exploiting this vulnerability allows an attacker with editor-level access to escalate privileges to full administrative control over the CMS, enabling them to modify content, change configurations, or potentially execute further attacks on the hosting environment. The vulnerability has a CVSS 3.1 base score of 8.8, reflecting its high impact and ease of exploitation over the network without user interaction. The issue was publicly disclosed on February 21, 2026, and fixed in version 2.3.4 of the software. No known exploits in the wild have been reported yet, but the risk remains significant due to the potential for complete system compromise.

Potential Impact

The impact of this vulnerability is critical for organizations using affected versions of the getformwork CMS. An attacker with editor-level credentials can escalate privileges to administrator, gaining full control over the CMS. This compromises confidentiality by exposing sensitive content and user data, integrity by allowing unauthorized content and configuration changes, and availability by potentially disabling or defacing the website. The flat file nature of the CMS may also expose additional risks if administrative access is leveraged to execute arbitrary code or access the underlying server. Organizations relying on getformwork for web content management face risks of reputational damage, data breaches, and operational disruption. Since the vulnerability requires only authenticated editor access, any compromised or malicious editor account can be weaponized, increasing the threat surface. The lack of known exploits in the wild does not diminish the urgency, as the vulnerability is straightforward to exploit and widely applicable to all affected versions.

Mitigation Recommendations

To mitigate this vulnerability, organizations should immediately upgrade getformwork CMS installations to version 2.3.4 or later, where the privilege enforcement issue is fixed. Until upgrading is possible, restrict editor role assignments and monitor account creation activities closely. Implement strict access controls to limit editor role assignments to trusted personnel only. Conduct audits of existing user accounts to identify and remove any unauthorized administrative accounts created by editors. Employ multi-factor authentication (MFA) for all CMS user accounts to reduce the risk of credential compromise. Additionally, monitor CMS logs for unusual account creation or privilege escalation activities. Consider isolating the CMS environment and applying web application firewalls (WAFs) with custom rules to detect and block suspicious requests related to account management. Finally, educate administrators and editors about the risks of privilege escalation and enforce the principle of least privilege in role assignments.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-18T19:47:02.155Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699a1a4cbe58cf853b44c9ee

Added to database: 2/21/2026, 8:49:16 PM

Last enriched: 2/21/2026, 8:49:48 PM

Last updated: 2/22/2026, 5:43:22 AM

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats