CWE-15: External Control of System or Configuration Setting Skip to content

Security weakness

CWE-15 External Control of System or Configuration Setting

A base-level weakness that can lead to effects that depend on context. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-15?

External Control of System or Configuration Setting: One or more system settings or configuration elements can be externally controlled by a user.

Business impact

What CWE-15 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Other

Effects that depend on context

The impact depends on where the weakness sits in your code and what it can reach.

Free security check

Is CWE-15 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-15

External Control of System or Configuration Setting

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

Weakness ID
CWE-15
Type
Base
Status
Incomplete
Applies to
ICS/OT
Introduced during
Implementation

Prevention

How to fix CWE-15, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Architecture and Design

    • 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.
    • 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.
    • 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 and evidence

How CWE-15 is found, and where it has hit

The testing methods MITRE recommends for finding it.

How it is detected

  • Automated Static AnalysisAutomated 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.

How we fix it

From finding to fixed: how Codefreex closes CWE-15

  1. 01

    Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. 02

    Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. 03

    Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. 04

    Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

FAQ

CWE-15: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-15?

CWE-15, “External Control of System or Configuration Setting”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. One or more system settings or configuration elements can be externally controlled by a user.

How serious is CWE-15?

It can affect other, with impacts such as varies by context. The real risk depends on where the weakness sits and what data or functions it exposes.

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. Ensure that. 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.

Can Codefreex check my site for CWE-15?

Yes. A senior engineer reviews your site, store or app for CWE-15 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Which technologies does CWE-15 affect?

MITRE lists it as applicable to ICS/OT. In practice any software that matches the weakness description can be affected, including custom code, plugins, themes and third-party libraries.

Free security check

Find out if CWE-15 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.