---
title: "CWE-15: External Control of System or Configuration Setting"
url: https://radicalnotion.ai/cwe/cwe-15
type: cwe
description: "One or more system settings or configuration elements can be externally controlled by a user."
updated: 2026-11-10
source: RadicalNotion.AI
license: CC BY-NC 4.0 (https://creativecommons.org/licenses/by-nc/4.0/)
---

# CWE-15: External Control of System or Configuration Setting

- **Abstraction:** Base
- **Structure:** Simple
- **Status:** Incomplete
- **CVEs with this as primary weakness:** 108
- **Of those, in CISA KEV:** 0
- **New in 2026:** 62
- **CWE catalog version:** 4.21

## Description

One or more system settings or configuration elements can be externally controlled by a user.

## Modes of introduction

| Phase | Note |
| --- | --- |
| Implementation | Setting manipulation vulnerabilities occur when an attacker can control values that govern the behavior of the system, manage specific resources, or in some way affect the functionality of the application. |
| Implementation | REALIZATION: This weakness is caused during implementation of an architectural security tactic. |

## Applicable platforms

**Technologies:** ICS/OT (Undetermined)

## Common consequences

| Scope | Impact | Note |
| --- | --- | --- |
| Other | Varies by Context | Allowing external control of system settings can disrupt service or cause an application to behave in unexpected, and potentially malicious ways. |

## Potential mitigations

### Architecture and Design (Separation of Privilege)

Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.

Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

### Implementation, Architecture and Design

Because setting manipulation covers a diverse set of functions, any attempt at illustrating it will inevitably be incomplete. Rather than searching for a tight-knit relationship between the functions addressed in the setting manipulation category, take a step back and consider the sorts of system values that an attacker should not be allowed to control.

### Implementation, Architecture and Design

In general, do not allow user-provided or otherwise untrusted data to control sensitive values. The leverage that an attacker gains by controlling these values is not always immediately obvious, but do not underestimate the creativity of the attacker.

## Detection methods

### Automated Static Analysis

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Effectiveness: High

## Demonstrative examples

### Example 1

The following C code accepts a number as one of its command line parameters and sets it as the host ID of the current machine.

Bad code:

```c
...
sethostid(argv[1]);
...
```

Although a process must be privileged to successfully invoke sethostid(), unprivileged users may be able to invoke the program. The code in this example allows user input to directly control the value of a system setting. If an attacker provides a malicious value for host ID, the attacker can misidentify the affected machine on the network or cause other unintended behavior.

### Example 2

The following Java code snippet reads a string from an HttpServletRequest and sets it as the active catalog for a database Connection.

Bad code:

```java
...
conn.setCatalog(request.getParameter("catalog"));
...
```

In this example, an attacker could cause an error by providing a nonexistent catalog name or connect to an unauthorized portion of the database.

## Real CVEs with this weakness (sample of 12 of 108)

| CVE | Title | Severity | CVSS | EPSS | CISA KEV | Published |
| --- | --- | --- | --- | --- | --- | --- |
| CVE-2026-87987 | - | critical | 10.0 | - | No | 2026-09-11 |
| CVE-2026-45087 | Dalfox: Unauthenticated Remote Code Execution via \`found-action\` in Dalfox Server Mode | critical | 10.0 | - | No | 2026-05-27 |
| CVE-2026-19593 | OpenAI Codex External Control of System or Configuration Setting Remote Code Execution Vulnerability | critical | 9.8 | - | No | 2026-09-01 |
| CVE-2024-4326 | Remote Code Execution via \`/apply\_settings\` and \`/execute\_code\` in parisneo/lollms-webui | critical | 9.8 | - | No | 2024-05-16 |
| CVE-2023-50252 | php-svg-lib unsafe attributes merge when parsing \`use\` tag | critical | 9.8 | - | No | 2023-12-12 |
| CVE-2026-46399 | Authenticated Remote Code Execution via File Overwrite | critical | 9.4 | - | No | 2026-06-05 |
| CVE-2026-95614 | Zenitel Connect host applies rsyslog configuration written to a volume shared with the hiatus container | critical | 9.3 | - | No | 2026-11-13 |
| CVE-2026-105294 | Legcord 1.1.0 through 1.3.0 Chromium Switch Injection via settings.setConfig | critical | 9.1 | - | No | 2026-10-05 |
| CVE-2024-39800 | Wavlink AC3000 openvpn.cgi openvpn\_server\_setup() Configuration Control Vulnerabilities | critical | 9.1 | - | No | 2025-01-14 |
| CVE-2024-39799 | Wavlink AC3000 openvpn.cgi openvpn\_server\_setup() Configuration Control Vulnerabilities | critical | 9.1 | - | No | 2025-01-14 |
| CVE-2024-39798 | Wavlink AC3000 openvpn.cgi openvpn\_server\_setup() Configuration Control Vulnerabilities | critical | 9.1 | - | No | 2025-01-14 |
| CVE-2024-38666 | Wavlink AC3000 openvpn.cgi openvpn\_client\_setup() Configuration Control Vulnerability | critical | 9.1 | - | No | 2025-01-14 |

## Related attack patterns (CAPEC)

- [CAPEC-13](https://radicalnotion.ai/capec/capec-13): Subverting Environment Variable Values
- [CAPEC-146](https://radicalnotion.ai/capec/capec-146): XML Schema Poisoning
- [CAPEC-176](https://radicalnotion.ai/capec/capec-176): Configuration/Environment Manipulation
- [CAPEC-203](https://radicalnotion.ai/capec/capec-203): Manipulate Registry Information
- [CAPEC-270](https://radicalnotion.ai/capec/capec-270): Modification of Registry Run Keys
- [CAPEC-271](https://radicalnotion.ai/capec/capec-271): Schema Poisoning
- [CAPEC-579](https://radicalnotion.ai/capec/capec-579): Replace Winlogon Helper DLL
- [CAPEC-69](https://radicalnotion.ai/capec/capec-69): Target Programs with Elevated Privileges
- [CAPEC-76](https://radicalnotion.ai/capec/capec-76): Manipulating Web Input to File System Calls
- [CAPEC-77](https://radicalnotion.ai/capec/capec-77): Manipulating User-Controlled Variables

## Related weaknesses

| Relationship | CWE | Name |
| --- | --- | --- |
| Parent | [CWE-20](https://radicalnotion.ai/cwe/cwe-20) | Improper Input Validation |
| Parent | [CWE-610](https://radicalnotion.ai/cwe/cwe-610) | Externally Controlled Reference to a Resource in Another Sphere |
| Parent | [CWE-642](https://radicalnotion.ai/cwe/cwe-642) | External Control of Critical State Data |

## Taxonomy mappings

| Taxonomy | Entry | Id | Fit |
| --- | --- | --- | --- |
| 7 Pernicious Kingdoms | Setting Manipulation | - | - |
| Software Fault Patterns | Tainted input to variable | SFP25 | - |

## Frequently asked questions

### What is CWE-15?

One or more system settings or configuration elements can be externally controlled by a user.

### What CVEs are caused by CWE-15?

108 recorded CVEs are attributed to CWE-15, including CVE-2026-87987, CVE-2026-45087 and CVE-2026-19593.

### How do you prevent CWE-15?

Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.

### How is CWE-15 detected?

Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

### What are the consequences of CWE-15?

Exploiting CWE-15 can lead to: Varies by Context.

### Is CWE-15 actively exploited?

108 recorded CVEs are caused by CWE-15; none are currently in CISA's KEV catalog of actively exploited flaws.

Primary source: [MITRE CWE](https://cwe.mitre.org/data/definitions/15.html)

---

Source: [RadicalNotion.AI](https://radicalnotion.ai/cwe/cwe-15). Licensed CC BY-NC 4.0; attribute RadicalNotion.AI and link the source page when you reuse this data.
