CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes
155 CVEs have CWE-915 as their primary weakness. 0 of them are in the CISA KEV catalog. The highest EPSS score among them is 44.543%.
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.
Child of CWE-913: Improper Control of Dynamically-Managed Code Resources
Mitigations
- Implementation: If available, use features of the language or framework that allow specification of allowlists of attributes or fields that are allowed to be modified. If possible, prefer allowlists over denylists. For applications written with Ruby on Rails, use the attr_accessible (allowlist) or attr_protected (denylist) macros in each class that may be used in mass assignment.
- Architecture and Design Implementation: If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- Implementation: For any externally-influenced input, check the input against an allowlist of internal object attributes or fields that are allowed to be modified.
- Implementation Architecture and Design: Refactor the code so that object attributes or fields do not need to be dynamically identified, and only expose getter/setter functionality for the intended attributes.
Observed examples
- CVE-2024-3283: Application for using LLMs allows modification of a sensitive variable using mass assignment.
- CVE-2012-2054: Mass assignment allows modification of arbitrary attributes using modified URL.
- CVE-2012-2055: Source version control product allows modification of trusted key using mass assignment.
- CVE-2008-7310: Attackers can bypass payment step in e-commerce product.
- CVE-2013-1465: Use of PHP unserialize function on untrusted input allows attacker to modify application configuration.
- CVE-2012-3527: Use of PHP unserialize function on untrusted input in content management system might allow code execution.
- CVE-2012-0911: PHP-based content management system written in PHP uses unserialize function on untrusted input to generate arbitrary objects, possibly allowing code execution.
- CVE-2011-4962: Content management system written in PHP allows code execution through page comments.
- CVE-2009-4137: Use of PHP unserialize function on cookie value allows remote code execution or upload of arbitrary files.
- CVE-2007-5741: Content management system written in Python interprets untrusted data as pickles, allowing code execution.
- CVE-2011-2520: Python script allows local users to execute code via pickled data.
- CVE-2005-2875: Python script allows remote attackers to execute arbitrary code using pickled objects.
- CVE-2013-0277: Ruby on Rails allows deserialization of untrusted YAML to execute arbitrary code.
- CVE-2011-2894: Spring framework allows deserialization of objects from untrusted sources to execute arbitrary code.
- CVE-2012-1833: Grails allows binding of arbitrary parameters to modify arbitrary object properties.
- CVE-2010-3258: Incorrect deserialization in web browser allows escaping the sandbox.
- CVE-2008-1013: Media library allows deserialization of objects by untrusted Java applets, leading to arbitrary code execution.
Top released CVEs
KEV first, then the highest EPSS score, the highest CVSS score and the newest.
| CVE | Published | Severity | CVSS | EPSS | Description |
|---|---|---|---|---|---|
| CVE-2026-129874 | 2026-11-16 | HIGH | 8.8 | 0.563% | REBUILD 3.5.0 through 4.5.4 contains a privilege escalation vulnerability that allows low-privileged authenticated users to modify their own roleId through… |
| CVE-2026-129550 | 2026-11-16 | CRITICAL | 9.1 | 0.395% | Tensei through 0.11.5 contains a privilege escalation vulnerability in @tensei/auth that allows unauthenticated or authenticated users to assign themselves… |
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-915'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-915'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).