CWE-287: Improper Authentication

What is CWE-287?

CWE-287 is Improper Authentication. The flaw arises when when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. The database currently holds 653 vulnerabilities mapped to CWE-287 and 9 of them are in the CISA Known Exploited Vulnerabilities catalog.

Analyzing data...

OWASP TOP 10:2025 RANK7 — A07:2025 — Authentication Failures
Related CVES (365 days)653
AbstractionClass
Likelihood of exploitHigh

Vulnerabilities mapped to CWE-287

653 vulnerabilities444% increase year over year

Vulnerabilities in CISA KEV for CWE-287

9 vulnerabilities350% increase year over year

Official definition

ByMitre CWE

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

Characteristics

Alternate terms

  • authentification — An alternate term is "authentification", which appears to be most commonly used by people from non-English-speaking countries.
  • AuthN — "AuthN" is typically used as an abbreviation of "authentication" within the web application security community. It is also distinct from "AuthZ," which is an abbreviation of "authorization." The use of "Auth" as an abbreviation is discouraged, since it could be used for either authentication or authorization.
  • AuthC — "AuthC" is used as an abbreviation of "authentication," but it appears to used less frequently than "AuthN."

Modes of introduction

  • Architecture and Design
  • Implementation: REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Common consequences

ImpactScopeExplanation
Read Application Data, Gain Privileges or Assume Identity, Execute Unauthorized Code or CommandsIntegrity, Confidentiality, Availability, Access ControlThis weakness can lead to the exposure of resources or functionality to unintended actors, possibly providing attackers with sensitive information or even execute arbitrary code.

Risk mitigations

  1. Libraries or Frameworks · Architecture and DesignUse an authentication framework or library such as the OWASP ESAPI Authentication feature.

Detection methods

MethodApproachEffectiveness
Automated Static AnalysisAutomated static analysis is useful for detecting certain types of authentication. A tool may be able to analyze related configuration files, such as .htaccess in Apache web servers, or detect the usage of commonly-used authentication libraries. Generally, automated static analysis tools have difficulty detecting custom authentication schemes. In addition, the software's design may include some functionality that is accessible to any user and does not require an established identity; an automated technique that detects the absence of authentication may report false positives.Limited
Manual Static AnalysisThis weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. Manual static analysis is useful for evaluating the correctness of custom authentication mechanisms.These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.High
Manual Static Analysis - Binary or BytecodeAccording to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Binary / Bytecode disassembler - then use manual analysis for vulnerabilities & anomaliesSOAR Partial
Dynamic Analysis with Automated Results InterpretationAccording to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Web Application Scanner Web Services Scanner Database ScannersSOAR Partial
Dynamic Analysis with Manual Results InterpretationAccording to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Fuzz Tester Framework-based FuzzerSOAR Partial
Manual Static Analysis - Source CodeAccording to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Manual Source Code Review (not inspections)SOAR Partial
Automated Static Analysis - Source CodeAccording to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Source code Weakness Analyzer Context-configured Source Code Weakness AnalyzerSOAR Partial
Automated Static AnalysisAccording to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Configuration CheckerSOAR Partial
Architecture or Design ReviewAccording to SOAR [REF-1479], the following detection techniques may be useful: ``` Highly cost effective: ``` Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.) Formal Methods / Correct-By-ConstructionHigh

Representative vulnerabilities

Below are representative vulnerabilities related to this CWE, prioritized by severity.

Sources (2)

CWE™ Program, operated by The MITRE Corporation. Copyright © 2006–2026, The MITRE Corporation. The MITRE Corporation hereby grants you a non-exclusive, royalty-free license to use CWE for research, development, and commercial purposes. CWE Terms of Use.

Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.