CWE-1287: Improper Validation of Specified Type of Input Skip to content

Security weakness

CWE-1287 Improper Validation of Specified Type of Input

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-1287?

Improper Validation of Specified Type of Input: The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type.

Business impact

What CWE-1287 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-1287 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-1287

Improper Validation of Specified Type of Input

The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type.

Weakness ID
CWE-1287
Type
Base
Status
Incomplete
Introduced during
Implementation

Prevention

How to fix CWE-1287, phase by phase

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

  1. 01

    Implementation

    • Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of.

Detection and evidence

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

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

Real vulnerabilities it caused

  • CVE-2024-37032Large language model (LLM) management tool does not validate the format of a digest value (CWE-1287) from a private, untrusted model registry, enabling relative path traversal (CWE-23), a.k.a. Probllama
  • CVE-2008-2223SQL injection through an ID that was supposed to be numeric.

How we fix it

From finding to fixed: how Codefreex closes CWE-1287

  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-1287: FAQs

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

What is CWE-1287?

CWE-1287, “Improper Validation of Specified Type of Input”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type.

How serious is CWE-1287?

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-1287?

Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into.

Can Codefreex check my site for CWE-1287?

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

Free security check

Find out if CWE-1287 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.