Formwork Improperly Managed Privileges in User creation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-27198: 0.46% estimated exploitation activity in the next 30 days; percentile 39.76 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Impact Successful exploitation allows an attacker to: - Gain full administrative control over the CMS. - Access all site data and user information. - Modify system configuration and security settings. - Create, modify, or delete any user account, including legitimate administrators. Patches Formwork 2.3.4 properly assigns roles on user creation.

Published by the source

19 Feb 2026, 20:31 UTC

Last modified by the source

23 Feb 2026, 22:27 UTC

Source last checked

26 Oct 2026, 14:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-34p4-7w83-35g2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-27198

Advisory: Formwork Improperly Managed Privileges in User creation
IDs: CVE-2026-27198, GHSA-34p4-7w83-35g2
Record: https://patchnext.com/advisories/cve-2026-27198 (revision 1, source checked 26 Oct 2026, 14:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: getformwork/formwork 2.3.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist getformwork/formwork: affected >= 2.0.0, <= 2.3.3; fixed in 2.3.4

## Suggested inspection (read-only)
- Packagist getformwork/formwork: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on getformwork/formwork.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-34p4-7w83-35g2 (GitHub-reviewed advisory GHSA-34p4-7w83-35g2 lists affected ranges: Packagist getformwork/formwork >=2.0.0 <=2.3.3)

Commands are suggestions: review each one before running it.