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: 04 July 2026 00:28 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: full · 11 mapping(s) from 2 framework(s): ATT&CK 10 (full) · OWASP-Web 1 (mostly)
OWASP Top 10 for Web (2025)
This weakness contributes to A06:2025 Insecure Design.
NIST 800-53 r5 controls that address this weakness (3)AI
| 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. |
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2025-54321 | 7.0 | 9.8 | 0.0041 | 2025-11-18 |
CVE-2021-41177 | 5.5 | 8.1 | 0.0150 | 2021-10-25 |
CVE-2023-35621 | 5.5 | 7.5 | 0.0234 | 2023-12-12 |
CVE-2024-32943 | 5.5 | 7.5 | 0.0048 | 2024-06-20 |
CVE-2024-35246 | 5.5 | 7.5 | 0.0048 | 2024-06-20 |
CVE-2024-6890 | 5.5 | 8.8 | 0.0072 | 2024-08-07 |
CVE-2024-45788 | 5.5 | 7.5 | 0.0050 | 2024-09-11 |
CVE-2024-47654 | 5.5 | 7.5 | 0.0047 | 2024-10-04 |
CVE-2025-57816 | 5.5 | 7.5 | 0.0041 | 2025-09-08 |
CVE-2026-24017 | 5.5 | 8.1 | 0.0076 | 2026-03-10 |
CVE-2026-30972 | 5.5 | 7.5 | 0.0034 | 2026-03-10 |
CVE-2026-32729 | 5.5 | 8.1 | 0.0034 | 2026-03-16 |
CVE-2026-7402 UPD | 5.5 | 8.1 | 0.0038 | 2026-04-30 |
CVE-2026-5233 | 5.5 | 7.1 | 0.0021 | 2026-06-15 |
CVE-2016-6543 | 3.5 | 5.9 | 0.0216 | 2018-07-13 |
CVE-2020-5141 | 3.5 | 6.5 | 0.0126 | 2020-10-12 |
CVE-2021-32678 | 3.5 | 3.7 | 0.0137 | 2021-07-12 |
CVE-2021-32703 | 3.5 | 5.3 | 0.0151 | 2021-07-12 |
CVE-2021-32705 | 3.5 | 5.3 | 0.0170 | 2021-07-12 |
CVE-2021-32741 | 3.5 | 5.3 | 0.0132 | 2021-07-12 |
CVE-2021-37191 | 3.5 | 4.3 | 0.0037 | 2021-09-14 |
CVE-2021-37910 | 3.5 | 3.7 | 0.0238 | 2021-11-12 |
CVE-2023-2758 | 3.5 | 3.7 | 0.0104 | 2023-05-31 |
CVE-2023-38068 | 3.5 | 6.5 | 0.0047 | 2023-07-12 |
CVE-2023-27279 | 3.5 | 6.5 | 0.0071 | 2024-04-19 |