CWE-470: Use of Externally-Controlled Input to Select Skip to content

Security weakness

CWE-470 Use of Externally-Controlled Input to Select Classes or Code

A base-level weakness that can lead to private data exposed, data, pages or code changed and downtime and lost sales. 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-470?

Use of Externally-Controlled Input to Select Classes or Code: The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.

Business impact

What CWE-470 could cost your business

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

Confidentiality

Private data exposed

Customer records, credentials, orders or internal files can be read by people who should never see them.

  • Execute Unauthorized Code or Commands
  • Alter Execution Logic
  • Read Application Data

Integrity

Data, pages or code changed

Prices, orders, content or the code your site runs can be altered without your approval.

  • Execute Unauthorized Code or Commands
  • Alter Execution Logic

Availability

Downtime and lost sales

Crashes, slowdowns or exhausted resources can take your site, store or app offline.

  • Execute Unauthorized Code or Commands
  • Alter Execution Logic
  • DoS: Crash, Exit, or Restart

Free security check

Is CWE-470 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-470

Use of Externally-Controlled Input to Select Classes or Code

The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.

An attacker could supply values to select unexpected classes or methods. If this occurs, then the attacker could create control flow paths that were not intended by the developer. These paths could bypass authentication or access control checks, or otherwise cause the product to behave in an unexpected manner. This situation becomes a doomsday scenario if the attacker can upload files into a location that appears on the product’s classpath (CWE-427) or add new entries to the product’s classpath (CWE-426). Under either of these conditions, the attacker can use reflection to introduce new, malicious behavior into the product.

Also known as: Reflection Injection, Unsafe Reflection

Weakness ID
CWE-470
Type
Base
Status
Draft
Applies to
Java, PHP, Interpreted
Introduced during
Architecture and Design, Implementation

Prevention

How to fix CWE-470, phase by phase

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

  1. 01

    Architecture and Design

    • Refactor your code to avoid using reflection.
    • Do not use user-controlled inputs to select and load classes or code.
  2. 02

    Implementation

    • Apply strict input validation by using allowlists or indirect selection to ensure that the user is only selecting allowable classes or code.

Detection and evidence

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

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

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.

Real vulnerabilities it caused

  • CVE-2018-1000613Cryptography API uses unsafe reflection when deserializing a private key
  • CVE-2004-2331Database system allows attackers to bypass sandbox restrictions by using the Reflection API.

How we fix it

From finding to fixed: how Codefreex closes CWE-470

  1. 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. 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. 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. Keep it fixed

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

FAQ

CWE-470: FAQs

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

What is CWE-470?

CWE-470, “Use of Externally-Controlled Input to Select Classes or Code”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.

How serious is CWE-470?

It can affect integrity, confidentiality, availability, other, with impacts such as execute unauthorized code or commands, alter execution logic, dos: crash, exit, or restart. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-470?

Refactor your code to avoid using reflection. Do not use user-controlled inputs to select and load classes or code.

Can Codefreex check my site for CWE-470?

Yes. A senior engineer reviews your site, store or app for CWE-470 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-470 affect?

MITRE lists it as applicable to Java, PHP, Interpreted. 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-470 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.