CWE · MITRE source
CWE-915Improperly Controlled Modification of Dynamically-Determined Object Attributes
The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.
If the object contains attributes that were only intended for internal use, then their unexpected modification could lead to a vulnerability. This weakness is sometimes known by the language-specific mechanisms that make it possible, such as mass assignment, autobinding, or object injection.
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: mostly · 5 mapping(s) from 2 framework(s): ATT&CK 4 (mostly) · OWASP-Web 1 (mostly)
OWASP Top 10 for Web (2025)
This weakness contributes to A08:2025 Software or Data Integrity Failures.
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
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-2024-0404 | 7.0 | 9.1 | 0.0078 | 2024-04-16 |
CVE-2024-5452 | 7.0 | 9.8 | 0.2649 | 2024-06-06 |
CVE-2024-55636 | 7.0 | 9.8 | 0.0090 | 2024-12-10 |
CVE-2024-55637 | 7.0 | 9.8 | 0.0080 | 2024-12-10 |
CVE-2024-55638 | 7.0 | 9.8 | 0.0096 | 2024-12-10 |
CVE-2025-68109 | 7.0 | 9.1 | 0.0138 | 2025-12-17 |
CVE-2026-22783 | 7.0 | 9.6 | 0.0030 | 2026-01-12 |
CVE-2026-29063 UPD | 7.0 | 9.8 | 0.0098 | 2026-03-06 |
CVE-2026-27591 | 7.0 | 9.9 | 0.0049 | 2026-03-11 |
CVE-2026-32640 UPD | 7.0 | 9.8 | 0.0051 | 2026-03-16 |
CVE-2026-33228 UPD | 7.0 | 9.8 | 0.0081 | 2026-03-20 |
CVE-2026-34208 | 7.0 | 10.0 | 0.0056 | 2026-04-06 |
CVE-2026-34179 | 7.0 | 9.1 | 0.0027 | 2026-04-09 |
CVE-2026-40569 | 7.0 | 9.0 | 0.0030 | 2026-04-21 |
CVE-2026-33453 UPD | 7.0 | 10.0 | 0.0616 | 2026-04-27 |
CVE-2025-69690 UPD | 7.0 | 9.1 | 0.0063 | 2026-05-08 |
CVE-2025-69691 UPD | 7.0 | 9.9 | 0.0053 | 2026-05-08 |
CVE-2026-48150 UPD | 7.0 | 9.0 | 0.0029 | 2026-05-27 |
CVE-2026-42861 UPD | 7.0 | 9.6 | 0.0025 | 2026-06-08 |
CVE-2026-46441 UPD | 7.0 | 9.6 | 0.0027 | 2026-06-08 |
CVE-2026-56142 | 7.0 | 9.9 | 0.0042 | 2026-06-19 |
CVE-2026-50160 | 7.0 | 10.0 | 0.0059 | 2026-07-01 |
CVE-2022-4068 | 6.0 | 5.4 | 0.3397 | 2022-11-20 |
CVE-2026-30822 | 6.0 | 7.7 | 0.1290 | 2026-03-07 |
CVE-2019-9057 | 5.5 | 8.8 | 0.0160 | 2019-03-26 |