CWE · MITRE source
CWE-841Improper Enforcement of Behavioral Workflow
The product supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence.
By performing actions in an unexpected order, or by omitting steps, an attacker could manipulate the business logic of the product or cause it to enter an invalid state. In some cases, this can also expose resultant weaknesses. For example, a file-sharing protocol might require that an actor perform separate steps to provide a username, then a password, before being able to transfer files. If the file-sharing server accepts a password command followed by a transfer command, without any username being provided, the product might still perform the transfer. Note that this is different than CWE-696, which focuses on when the product performs actions in the wrong sequence; this entry is closely related, but it is focused on ensuring that the actor performs actions in the correct sequence. Workflow-related behaviors include:
Last updated: 20 August 2026 14:15 UTC
OWASP Top 10 for Web (2025)
This weakness contributes to A06:2025 Insecure Design.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
—
—
V7.2.1
NIST 800-53 r5 controls that address this weakness (0)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2022-2105 UPD | 7.3 | 9.4 | 0.0106 | 2022-06-24 |
CVE-2025-48481 UPD | 7.3 | 9.8 | 0.0049 | 2025-05-30 |
CVE-2026-3130 | 7.3 | 9.8 | 0.0045 | 2026-03-03 |
CVE-2026-30783 UPD | 7.3 | 9.8 | 0.0038 | 2026-03-05 |
CVE-2022-2102 UPD | 7.2 | 9.4 | 0.0090 | 2022-06-24 |
CVE-2026-34582 UPD | 6.7 | 9.1 | 0.0023 | 2026-04-07 |
CVE-2025-48476 UPD | 6.6 | 8.8 | 0.0049 | 2025-05-30 |
CVE-2026-43937 UPD | 6.6 | 8.8 | 0.0049 | 2026-05-12 |
CVE-2024-51738 UPD | 6.2 | 8.1 | 0.0058 | 2025-01-20 |
CVE-2022-1667 UPD | 6.1 | 7.5 | 0.0123 | 2022-06-24 |
CVE-2025-48477 UPD | 6.1 | 8.1 | 0.0045 | 2025-05-30 |
CVE-2024-46307 UPD | 5.9 | 7.5 | 0.0046 | 2024-10-09 |
CVE-2026-43974 UPD | 5.9 | 7.5 | 0.0048 | 2026-06-08 |
CVE-2026-30574 | 5.7 | 7.5 | 0.0026 | 2026-03-27 |
CVE-2026-41259 | 5.7 | 7.5 | 0.0021 | 2026-04-23 |
CVE-2026-42246 UPD | 5.6 | 7.4 | 0.0031 | 2026-05-09 |
CVE-2026-48505 | 5.6 | 7.4 | 0.0030 | 2026-06-22 |
CVE-2024-0410 UPD | 5.5 | 7.7 | 0.0046 | 2024-02-22 |
CVE-2025-52469 | 5.4 | 7.1 | 0.0029 | 2026-03-02 |
CVE-2023-5921 UPD | 5.3 | 7.1 | 0.0025 | 2023-11-22 |
CVE-2025-58051 UPD | 5.1 | 6.5 | 0.0050 | 2025-10-16 |
CVE-2026-46540 UPD | 5.0 | 6.5 | 0.0026 | 2026-06-10 |
CVE-2024-13065 UPD | 4.8 | 6.3 | 0.0020 | 2025-09-03 |
CVE-2025-55330 UPD | 4.8 | 6.1 | 0.0054 | 2025-10-14 |
CVE-2025-55332 UPD | 4.8 | 6.1 | 0.0054 | 2025-10-14 |