CWE · MITRE source
CWE-799Improper Control of Interaction Frequency
The product does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests.
This can allow the actor to perform actions more frequently than expected. The actor could be a human or an automated process such as a virus or bot. This could be used to cause a denial of service, compromise program logic (such as limiting humans to a single vote), or other consequences. For example, an authentication routine might not limit the number of times an attacker can guess a password. Or, a web site might conduct a poll but only expect humans to vote a maximum of once a day.
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.
NIST 800-53 r5 controls that address this weakness (3)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
PL-6 | Security-related Activity Planning | PL | The control requires defining frequency, timing, and approval for security interactions, directly addressing uncontrolled interaction rates. |
SC-6 | Resource Availability | SC | Allocation policies inherently restrict interaction frequency, reducing the impact of excessive requests. |
SI-8 | Spam Protection | SI | Spam protection explicitly controls interaction frequency by detecting and acting on bulk unsolicited messages from external sources. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2025-54321 | 7.3 | 9.8 | 0.0047 | 2025-11-18 |
CVE-2024-6890 UPD | 6.7 | 8.8 | 0.0072 | 2024-08-07 |
CVE-2021-41177 UPD | 6.4 | 8.1 | 0.0155 | 2021-10-25 |
CVE-2023-35621 UPD | 6.3 | 7.5 | 0.0234 | 2023-12-12 |
CVE-2026-24017 | 6.2 | 8.1 | 0.0076 | 2026-03-10 |
CVE-2026-7402 UPD | 6.1 | 8.1 | 0.0038 | 2026-04-30 |
CVE-2026-32729 | 6.0 | 8.1 | 0.0034 | 2026-03-16 |
CVE-2024-32943 UPD | 5.9 | 7.5 | 0.0048 | 2024-06-20 |
CVE-2024-35246 UPD | 5.9 | 7.5 | 0.0048 | 2024-06-20 |
CVE-2024-45788 UPD | 5.9 | 7.5 | 0.0050 | 2024-09-11 |
CVE-2024-47654 UPD | 5.9 | 7.5 | 0.0049 | 2024-10-04 |
CVE-2025-57816 | 5.8 | 7.5 | 0.0043 | 2025-09-08 |
CVE-2026-30972 | 5.8 | 7.5 | 0.0034 | 2026-03-10 |
CVE-2020-5141 UPD | 5.4 | 6.5 | 0.0128 | 2020-10-12 |
CVE-2026-5233 | 5.3 | 7.1 | 0.0021 | 2026-06-15 |
CVE-2023-38068 UPD | 5.2 | 6.5 | 0.0055 | 2023-07-12 |
CVE-2023-27279 UPD | 5.2 | 6.5 | 0.0071 | 2024-04-19 |
CVE-2026-54738 | 5.2 | 6.5 | 0.0043 | 2026-08-19 |
CVE-2016-6543 UPD | 5.1 | 5.9 | 0.0216 | 2018-07-13 |
CVE-2024-34695 UPD | 5.1 | 6.3 | 0.0076 | 2024-05-14 |
CVE-2023-40673 UPD | 5.1 | 6.5 | 0.0040 | 2024-06-04 |
CVE-2024-51557 | 5.1 | 6.5 | 0.0047 | 2024-11-04 |
CVE-2024-8475 UPD | 5.1 | 6.5 | 0.0038 | 2024-12-17 |
CVE-2026-22216 | 5.1 | 6.5 | 0.0032 | 2026-03-13 |
CVE-2024-57603 UPD | 5.0 | 6.3 | 0.0044 | 2025-02-12 |