Security reference
CWE directory: software weaknesses explained
613 weaknesses from MITRE’s Common Weakness Enumeration with their impact, fixes and detection methods, plus plain-English guidance for the ones that hit websites, stores and apps most.
Quick answer
What is the CWE directory?
The Codefreex CWE directory is a free reference to 613 software weaknesses from MITRE’s Common Weakness Enumeration. Each page gives the official definition, what can go wrong, how to prevent it and how it is detected, with plain-English fixes for the weaknesses most common in websites and web applications.
2025 CWE Top 25
The most dangerous software weaknesses
MITRE’s ranking of the weakness types behind the most serious publicly reported vulnerabilities.
Cross-site scripting (XSS)
Attackers plant scripts in your pages that run in visitors’ browsers and can hijack their sessions or accounts.
02CWE-89SQL injection (SQLi)
Untrusted input changes your database queries, letting attackers read, alter or delete the data your business runs on.
03CWE-352Cross-site request forgery (CSRF)
Another website tricks a logged-in user’s browser into sending actions to your site that the user never intended.
04CWE-862Missing authorization
Your site performs an action or shows data without checking whether the person asking is allowed to.
05CWE-787Out-of-bounds write
Software writes data outside the memory it reserved, which can crash it or let attackers run their own code.
06CWE-22Path traversal
Attackers manipulate a file path your site accepts to read or overwrite files outside the folder you intended.
07CWE-416Use after free (UAF)
A program keeps using memory after releasing it, which can cause crashes, data leaks or attacker-controlled code execution.
08CWE-125Out-of-bounds read
Software reads memory outside the area it should, which can leak secrets or crash the program.
09CWE-78OS command injection
Untrusted input reaches a system command your server runs, letting attackers execute their own commands on it.
10CWE-94Code injection
Your application builds and runs code from untrusted input, so attackers can make it execute instructions they wrote.
11CWE-120Classic buffer overflow
A program copies input into a fixed-size memory buffer without checking that it fits, corrupting nearby memory.
12CWE-434Unrestricted file upload
Your site accepts uploaded files without proper checks, so an attacker can upload a file the server will run.
13CWE-476Null pointer dereference
A program tries to use a reference that points to nothing, which usually makes it crash or stop responding.
14CWE-121Stack-based buffer overflow
A program writes past a buffer on its call stack, causing crashes or handing control to an attacker.
15CWE-502Insecure deserialization
Your application rebuilds objects from data an attacker can modify, which can lead to tampering or code execution.
16CWE-122Heap-based buffer overflow
A program writes past a dynamically allocated memory block, corrupting nearby data and risking crashes or code execution.
17CWE-863Incorrect authorization
Your site checks permissions, but the check is flawed, so some users get access they should not have.
18CWE-20Improper input validation
Your site accepts data without checking it properly, so unexpected values can crash it or corrupt records.
19CWE-284Broken access control
People can reach pages, data or actions on your site that should be off limits to them.
20CWE-200Information disclosure
Your site reveals private data or technical details to people who were never meant to see them.
21CWE-306Missing authentication
An important feature on your site works without a login, so anyone who finds it can use it.
22CWE-918Server-side request forgery (SSRF)
An attacker tricks your server into fetching addresses of their choosing, including systems only your server can reach.
23CWE-77Command injection
User input ends up inside a command your server runs, letting an attacker change what that command does.
24CWE-639Insecure direct object reference (IDOR)
Changing an ID in a link or request lets one user open or edit another user’s records.
25CWE-770Missing resource limits
Your site lets one visitor use unlimited requests, memory or storage, which can slow or stop it for everyone.
Websites and apps
Common weaknesses in websites, stores and web apps
Authentication, sessions, configuration and data handling problems we see most in real projects.
Verbose error messages
Error pages reveal technical details, such as file paths or database queries, that help an attacker plan.
CWE-269Improper privilege management
Accounts or programs end up with more power than they should have, or can raise their own access.
CWE-276Incorrect default permissions
Files, folders or cloud storage are created with access that is far wider than they need.
CWE-287Broken authentication
Your site accepts someone’s claim about who they are without properly proving it, so attackers can pose as real users.
CWE-307Missing brute-force protection
Your login accepts unlimited password guesses, so automated tools can keep trying until one works.
CWE-312Cleartext storage of sensitive data
Sensitive data is stored unencrypted, so anyone who reaches the file or database can simply read it.
CWE-319Unencrypted data transmission
Sensitive data travels between systems without encryption, so anyone on the network path can read or alter it.
CWE-327Weak or broken encryption
Your site protects data with an outdated or homemade cryptographic method that a determined attacker may be able to break.
CWE-384Session fixation
An attacker plants a session ID on a visitor, waits for the login, then takes over the account.
CWE-400Resource exhaustion (denial of service)
Your site lets one user consume unlimited memory, processing power or storage until it slows down or stops.
CWE-521Weak password requirements
Your site accepts short, common or previously leaked passwords, which makes customer and admin accounts easy to break into.
CWE-522Weakly protected credentials
Passwords or login tokens are stored or sent in a way that lets someone else capture and reuse them.
CWE-532Sensitive data in logs
Passwords, tokens or customer details get written to log files that far more people and systems can read.
CWE-601Open redirect
A link on your trusted domain can be altered to send visitors to a site an attacker controls.
CWE-611XML external entity (XXE)
An XML file your server processes can instruct it to read local files or contact other systems.
CWE-614Cookie missing Secure flag
Login cookies can be sent over unencrypted connections, where others on the same network may capture them.
CWE-640Weak password reset mechanism
A flawed forgot-password process lets someone take over an account without ever knowing the real password.
CWE-798Hard-coded credentials
Passwords, API keys or secret keys are written directly into your code, where others can find and reuse them.
CWE-829Untrusted third-party code inclusion
Your site runs code loaded from a source you do not control, so its problems become yours.
CWE-915Mass assignment
Your app saves every field a request sends, including ones users should never be allowed to change.
CWE-942Permissive cross-domain policy (CORS)
Your site’s browser security policy trusts domains it should not, letting other websites read data or run scripts.
CWE-1004Cookie missing HttpOnly flag
Login cookies can be read by scripts running on the page, so one script flaw can expose sessions.
CWE-1021Clickjacking (UI redressing)
Another site loads your page in a hidden frame and tricks visitors into clicking things they cannot see.
CWE-1104Unmaintained third-party components
Your site depends on plugins or libraries nobody maintains, so newly found security flaws never get fixed.
CWE-1321Prototype pollution
Crafted input changes the shared template behind every JavaScript object, altering how your whole application behaves.
Full index
All 613 weaknesses
Search by number or name.
- CWE-6J2EE Misconfiguration: Insufficient Session-ID Length
- CWE-7J2EE Misconfiguration: Missing Custom Error Page
- CWE-8J2EE Misconfiguration: Entity Bean Declared Remote
- CWE-9J2EE Misconfiguration: Weak Access Permissions for EJB Methods
- CWE-11ASP.NET Misconfiguration: Creating Debug Binary
- CWE-12ASP.NET Misconfiguration: Missing Custom Error Page
- CWE-14Compiler Removal of Code to Clear Buffers
- CWE-15External Control of System or Configuration Setting
- CWE-20Improper input validation
- CWE-22Path traversal
- CWE-23Relative Path Traversal
- CWE-24Path Traversal: ‘../filedir’
- CWE-25Path Traversal: ‘/../filedir’
- CWE-26Path Traversal: ‘/dir/../filename’
- CWE-27Path Traversal: ‘dir/../../filename’
- CWE-28Path Traversal: ‘..\filedir’
- CWE-29Path Traversal: ‘\..\filename’
- CWE-30Path Traversal: ‘\dir\..\filename’
- CWE-31Path Traversal: ‘dir\..\..\filename’
- CWE-32Path Traversal: ‘…’
- CWE-33Path Traversal: ‘….’
- CWE-34Path Traversal: ‘….//’
- CWE-35Path Traversal: ‘…/…//’
- CWE-36Absolute Path Traversal
- CWE-37Path Traversal: ‘/absolute/pathname/here’
- CWE-38Path Traversal: ‘\absolute\pathname\here’
- CWE-39Path Traversal: ‘C:dirname’
- CWE-40Path Traversal: ‘\\UNC\share\name\’
- CWE-41Improper Resolution of Path Equivalence
- CWE-50Path Equivalence: ‘//multiple/leading/slash’
- CWE-55Path Equivalence: ‘/./’
- CWE-59Improper Link Resolution Before File Access
- CWE-61UNIX Symbolic Link (Symlink) Following
- CWE-62UNIX Hard Link
- CWE-64Windows Shortcut Following
- CWE-65Windows Hard Link
- CWE-66Improper Handling of File Names that Identify Virtual Resources
- CWE-67Improper Handling of Windows Device Names
- CWE-73External Control of File Name or Path
- CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component
- CWE-77Command injection
- CWE-78OS command injection
- CWE-79Cross-site scripting (XSS)
- CWE-80Improper Neutralization of Script-Related HTML Tags in a Web Page
- CWE-81Improper Neutralization of Script in an Error Message Web Page
- CWE-82Improper Neutralization of Script in Attributes of IMG Tags in a Web Page
- CWE-83Improper Neutralization of Script in Attributes in a Web Page
- CWE-84Improper Neutralization of Encoded URI Schemes in a Web Page
- CWE-85Doubled Character XSS Manipulations
- CWE-86Improper Neutralization of Invalid Characters in Identifiers in Web Pages
- CWE-87Improper Neutralization of Alternate XSS Syntax
- CWE-88Improper Neutralization of Argument Delimiters in a Command
- CWE-89SQL injection (SQLi)
- CWE-90Improper Neutralization of Special Elements used in an LDAP Query
- CWE-91XML Injection
- CWE-93Improper Neutralization of CRLF Sequences
- CWE-94Code injection
- CWE-95Improper Neutralization of Directives in Dynamically Evaluated Code
- CWE-96Improper Neutralization of Directives in Statically Saved Code
- CWE-98Improper Control of Filename for Include/Require Statement in PHP Program
- CWE-99Improper Control of Resource Identifiers
- CWE-102Struts: Duplicate Validation Forms
- CWE-103Struts: Incomplete validate() Method Definition
- CWE-104Struts: Form Bean Does Not Extend Validation Class
- CWE-105Struts: Form Field Without Validator
- CWE-106Struts: Plug-in Framework not in Use
- CWE-108Struts: Unvalidated Action Form
- CWE-112Missing XML Validation
- CWE-113Improper Neutralization of CRLF Sequences in HTTP Headers
- CWE-114Process Control
- CWE-116Improper Encoding or Escaping of Output
- CWE-117Improper Output Neutralization for Logs
- CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer
- CWE-120Classic buffer overflow
- CWE-121Stack-based buffer overflow
- CWE-122Heap-based buffer overflow
- CWE-123Write-what-where Condition
- CWE-124Buffer Underwrite
- CWE-125Out-of-bounds read
- CWE-126Buffer Over-read
- CWE-127Buffer Under-read
- CWE-128Wrap-around Error
- CWE-129Improper Validation of Array Index
- CWE-130Improper Handling of Length Parameter Inconsistency
- CWE-131Incorrect Calculation of Buffer Size
- CWE-134Use of Externally-Controlled Format String
- CWE-135Incorrect Calculation of Multi-Byte String Length
- CWE-138Improper Neutralization of Special Elements
- CWE-140Improper Neutralization of Delimiters
- CWE-141Improper Neutralization of Parameter/Argument Delimiters
- CWE-142Improper Neutralization of Value Delimiters
- CWE-143Improper Neutralization of Record Delimiters
- CWE-144Improper Neutralization of Line Delimiters
- CWE-145Improper Neutralization of Section Delimiters
- CWE-146Improper Neutralization of Expression/Command Delimiters
- CWE-147Improper Neutralization of Input Terminators
- CWE-148Improper Neutralization of Input Leaders
- CWE-149Improper Neutralization of Quoting Syntax
- CWE-150Improper Neutralization of Escape, Meta, or Control Sequences
- CWE-151Improper Neutralization of Comment Delimiters
- CWE-152Improper Neutralization of Macro Symbols
- CWE-153Improper Neutralization of Substitution Characters
- CWE-154Improper Neutralization of Variable Name Delimiters
- CWE-155Improper Neutralization of Wildcards or Matching Symbols
- CWE-156Improper Neutralization of Whitespace
- CWE-157Failure to Sanitize Paired Delimiters
- CWE-158Improper Neutralization of Null Byte or NUL Character
- CWE-159Improper Handling of Invalid Use of Special Elements
- CWE-160Improper Neutralization of Leading Special Elements
- CWE-161Improper Neutralization of Multiple Leading Special Elements
- CWE-162Improper Neutralization of Trailing Special Elements
- CWE-163Improper Neutralization of Multiple Trailing Special Elements
- CWE-164Improper Neutralization of Internal Special Elements
- CWE-165Improper Neutralization of Multiple Internal Special Elements
- CWE-166Improper Handling of Missing Special Element
- CWE-167Improper Handling of Additional Special Element
- CWE-168Improper Handling of Inconsistent Special Elements
- CWE-170Improper Null Termination
- CWE-172Improper Encoding or Decoding of Data
- CWE-173Improper Handling of Alternate Encoding
- CWE-174Double Decoding of the Same Data
- CWE-175Improper Handling of Mixed Encoding
- CWE-176Improper Handling of Unicode Encoding
- CWE-177Improper Handling of URL Encoding
- CWE-178Improper Handling of Case Sensitivity
- CWE-179Incorrect Behavior Order: Early Validation
- CWE-180Incorrect Behavior Order: Validate Before Canonicalize
- CWE-182Collapse of Data into Unsafe Value
- CWE-183Permissive List of Allowed Inputs
- CWE-184Incomplete List of Disallowed Inputs
- CWE-185Incorrect Regular Expression
- CWE-187Partial String Comparison
- CWE-188Reliance on Data/Memory Layout
- CWE-190Integer Overflow or Wraparound
- CWE-191Integer Underflow
- CWE-192Integer Coercion Error
- CWE-193Off-by-one Error
- CWE-194Unexpected Sign Extension
- CWE-195Signed to Unsigned Conversion Error
- CWE-196Unsigned to Signed Conversion Error
- CWE-197Numeric Truncation Error
- CWE-200Information disclosure
- CWE-201Insertion of Sensitive Information Into Sent Data
- CWE-203Observable Discrepancy
- CWE-204Observable Response Discrepancy
- CWE-206Observable Internal Behavioral Discrepancy
- CWE-207Observable Behavioral Discrepancy With Equivalent Products
- CWE-208Observable Timing Discrepancy
- CWE-209Verbose error messages
- CWE-211Externally-Generated Error Message Containing Sensitive Information
- CWE-212Improper Removal of Sensitive Information Before Storage or Transfer
- CWE-215Insertion of Sensitive Information Into Debugging Code
- CWE-226Sensitive Information in Resource Not Removed Before Reuse
- CWE-233Improper Handling of Parameters
- CWE-234Failure to Handle Missing Parameter
- CWE-241Improper Handling of Unexpected Data Type
- CWE-242Use of Inherently Dangerous Function
- CWE-244Improper Clearing of Heap Memory Before Release
- CWE-246J2EE Bad Practices: Direct Use of Sockets
- CWE-248Uncaught Exception
- CWE-250Execution with Unnecessary Privileges
- CWE-252Unchecked Return Value
- CWE-253Incorrect Check of Function Return Value
- CWE-256Plaintext Storage of a Password
- CWE-257Storing Passwords in a Recoverable Format
- CWE-258Empty Password in Configuration File
- CWE-259Use of Hard-coded Password
- CWE-260Password in Configuration File
- CWE-262Not Using Password Aging
- CWE-263Password Aging with Long Expiration
- CWE-266Incorrect Privilege Assignment
- CWE-267Privilege Defined With Unsafe Actions
- CWE-268Privilege Chaining
- CWE-269Improper privilege management
- CWE-270Privilege Context Switching Error
- CWE-271Privilege Dropping / Lowering Errors
- CWE-272Least Privilege Violation
- CWE-273Improper Check for Dropped Privileges
- CWE-276Incorrect default permissions
- CWE-279Incorrect Execution-Assigned Permissions
- CWE-280Improper Handling of Insufficient Permissions or Privileges
- CWE-284Broken access control
- CWE-285Improper Authorization
- CWE-287Broken authentication
- CWE-288Authentication Bypass Using an Alternate Path or Channel
- CWE-289Authentication Bypass by Alternate Name
- CWE-291Reliance on IP Address for Authentication
- CWE-293Using Referer Field for Authentication
- CWE-294Authentication Bypass by Capture-replay
- CWE-295Improper Certificate Validation
- CWE-296Improper Following of a Certificate’s Chain of Trust
- CWE-297Improper Validation of Certificate with Host Mismatch
- CWE-298Improper Validation of Certificate Expiration
- CWE-299Improper Check for Certificate Revocation
- CWE-300Channel Accessible by Non-Endpoint
- CWE-301Reflection Attack in an Authentication Protocol
- CWE-306Missing authentication
- CWE-307Missing brute-force protection
- CWE-309Use of Password System for Primary Authentication
- CWE-311Missing Encryption of Sensitive Data
- CWE-312Cleartext storage of sensitive data
- CWE-313Cleartext Storage in a File or on Disk
- CWE-315Cleartext Storage of Sensitive Information in a Cookie
- CWE-318Cleartext Storage of Sensitive Information in Executable
- CWE-319Unencrypted data transmission
- CWE-321Use of Hard-coded Cryptographic Key
- CWE-322Key Exchange without Entity Authentication
- CWE-323Reusing a Nonce, Key Pair in Encryption
- CWE-326Inadequate Encryption Strength
- CWE-327Weak or broken encryption
- CWE-328Use of Weak Hash
- CWE-329Generation of Predictable IV with CBC Mode
- CWE-330Use of Insufficiently Random Values
- CWE-331Insufficient Entropy
- CWE-332Insufficient Entropy in PRNG
- CWE-335Incorrect Usage of Seeds in Pseudo-Random Number Generator
- CWE-336Same Seed in Pseudo-Random Number Generator
- CWE-337Predictable Seed in Pseudo-Random Number Generator
- CWE-338Use of Cryptographically Weak Pseudo-Random Number Generator
- CWE-339Small Seed Space in PRNG
- CWE-340Generation of Predictable Numbers or Identifiers
- CWE-341Predictable from Observable State
- CWE-346Origin Validation Error
- CWE-350Reliance on Reverse DNS Resolution for a Security-Critical Action
- CWE-352Cross-site request forgery (CSRF)
- CWE-353Missing Support for Integrity Check
- CWE-354Improper Validation of Integrity Check Value
- CWE-356Missing User Interaction for Potentially Unsafe Action
- CWE-358Improperly Implemented Security Check for Standard
- CWE-359Exposure of Private Personal Information to an Unauthorized Actor
- CWE-362Concurrent Execution using Shared Resource with Improper Synchronization
- CWE-363Race Condition Enabling Link Following
- CWE-364Signal Handler Race Condition
- CWE-366Race Condition within a Thread
- CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
- CWE-368Context Switching Race Condition
- CWE-369Divide By Zero
- CWE-370Missing Check for Certificate Revocation after Initial Check
- CWE-378Creation of Temporary File With Insecure Permissions
- CWE-379Creation of Temporary File in Directory with Insecure Permissions
- CWE-382J2EE Bad Practices: Use of System.exit
- CWE-384Session fixation
- CWE-390Detection of Error Condition Without Action
- CWE-392Missing Report of Error Condition
- CWE-393Return of Wrong Status Code
- CWE-394Unexpected Status Code or Return Value
- CWE-395Use of NullPointerException Catch to Detect NULL Pointer Dereference
- CWE-396Declaration of Catch for Generic Exception
- CWE-397Declaration of Throws for Generic Exception
- CWE-400Resource exhaustion (denial of service)
- CWE-401Missing Release of Memory after Effective Lifetime
- CWE-403Exposure of File Descriptor to Unintended Control Sphere
- CWE-404Improper Resource Shutdown or Release
- CWE-405Asymmetric Resource Consumption
- CWE-406Insufficient Control of Network Message Volume
- CWE-407Inefficient Algorithmic Complexity
- CWE-412Unrestricted Externally Accessible Lock
- CWE-413Improper Resource Locking
- CWE-415Double Free
- CWE-416Use after free (UAF)
- CWE-420Unprotected Alternate Channel
- CWE-426Untrusted Search Path
- CWE-427Uncontrolled Search Path Element
- CWE-428Unquoted Search Path or Element
- CWE-431Missing Handler
- CWE-433Unparsed Raw Web Content Delivery
- CWE-434Unrestricted file upload
- CWE-441Unintended Proxy or Intermediary
- CWE-444Inconsistent Interpretation of HTTP Requests
- CWE-450Multiple Interpretations of UI Input
- CWE-451User Interface (UI) Misrepresentation of Critical Information
- CWE-453Insecure Default Variable Initialization
- CWE-454External Initialization of Trusted Variables or Data Stores
- CWE-456Missing Initialization of a Variable
- CWE-457Use of Uninitialized Variable
- CWE-459Incomplete Cleanup
- CWE-462Duplicate Key in Associative List
- CWE-463Deletion of Data Structure Sentinel
- CWE-464Addition of Data Structure Sentinel
- CWE-467Use of sizeof() on a Pointer Type
- CWE-469Use of Pointer Subtraction to Determine Size
- CWE-470Use of Externally-Controlled Input to Select Classes or Code
- CWE-472External Control of Assumed-Immutable Web Parameter
- CWE-473PHP External Variable Modification
- CWE-474Use of Function with Inconsistent Implementations
- CWE-476Null pointer dereference
- CWE-477Use of Obsolete Function
- CWE-478Missing Default Case in Multiple Condition Expression
- CWE-479Signal Handler Use of a Non-reentrant Function
- CWE-480Use of Incorrect Operator
- CWE-483Incorrect Block Delimitation
- CWE-484Omitted Break Statement in Switch
- CWE-486Comparison of Classes by Name
- CWE-487Reliance on Package-level Scope
- CWE-488Exposure of Data Element to Wrong Session
- CWE-489Active Debug Code
- CWE-492Use of Inner Class Containing Sensitive Data
- CWE-493Critical Public Variable Without Final Modifier
- CWE-494Download of Code Without Integrity Check
- CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere
- CWE-498Cloneable Class Containing Sensitive Information
- CWE-499Serializable Class Containing Sensitive Data
- CWE-500Public Static Field Not Marked Final
- CWE-502Insecure deserialization
- CWE-506Embedded Malicious Code
- CWE-510Trapdoor
- CWE-515Covert Storage Channel
- CWE-521Weak password requirements
- CWE-522Weakly protected credentials
- CWE-523Unprotected Transport of Credentials
- CWE-524Use of Cache Containing Sensitive Information
- CWE-525Use of Web Browser Cache Containing Sensitive Information
- CWE-526Cleartext Storage of Sensitive Information in an Environment Variable
- CWE-530Exposure of Backup File to an Unauthorized Control Sphere
- CWE-532Sensitive data in logs
- CWE-540Inclusion of Sensitive Information in Source Code
- CWE-543Use of Singleton Pattern Without Synchronization in a Multithreaded Context
- CWE-547Use of Hard-coded, Security-relevant Constants
- CWE-548Exposure of Information Through Directory Listing
- CWE-552Files or Directories Accessible to External Parties
- CWE-554ASP.NET Misconfiguration: Not Using Input Validation Framework
- CWE-558Use of getlogin() in Multithreaded Application
- CWE-561Dead Code
- CWE-562Return of Stack Variable Address
- CWE-564Use of Hibernate with HQL/SQL Query String Containing External Input
- CWE-565Reliance on Cookies without Validation and Integrity Checking
- CWE-566Authorization Bypass Through User-Controlled SQL Primary Key
- CWE-567Unsynchronized Access to Shared Data in a Multithreaded Context
- CWE-573Improper Following of Specification by Caller
- CWE-574EJB Bad Practices: Use of Synchronization Primitives
- CWE-575EJB Bad Practices: Use of AWT Swing
- CWE-576EJB Bad Practices: Use of Java I/O
- CWE-582Array Declared Public, Final, and Static
- CWE-583finalize() Method Declared Public
- CWE-585Empty Synchronized Block
- CWE-586Explicit Call to Finalize
- CWE-587Assignment of a Fixed Address to a Pointer
- CWE-588Attempt to Access Child of a Non-structure Pointer
- CWE-589Call to Non-ubiquitous API
- CWE-590Free of Memory not on the Heap
- CWE-594J2EE Framework: Saving Unserializable Objects to Disk
- CWE-595Comparison of Object References Instead of Object Contents
- CWE-597Use of Wrong Operator in String Comparison
- CWE-598Use of HTTP Request With Sensitive Query String
- CWE-599Missing Validation of OpenSSL Certificate
- CWE-601Open redirect
- CWE-602Client-Side Enforcement of Server-Side Security
- CWE-609Double-Checked Locking
- CWE-610Externally Controlled Reference to a Resource in Another Sphere
- CWE-611XML external entity (XXE)
- CWE-614Cookie missing Secure flag
- CWE-615Inclusion of Sensitive Information in Source Code Comments
- CWE-616Incomplete Identification of Uploaded File Variables
- CWE-617Reachable Assertion
- CWE-618Exposed Unsafe ActiveX Method
- CWE-620Unverified Password Change
- CWE-621Variable Extraction Error
- CWE-624Executable Regular Expression Error
- CWE-625Permissive Regular Expression
- CWE-626Null Byte Interaction Error
- CWE-627Dynamic Variable Evaluation
- CWE-628Function Call with Incorrectly Specified Arguments
- CWE-636Not Failing Securely
- CWE-637Unnecessary Complexity in Protection Mechanism
- CWE-638Not Using Complete Mediation
- CWE-639Insecure direct object reference (IDOR)
- CWE-640Weak password reset mechanism
- CWE-641Improper Restriction of Names for Files and Other Resources
- CWE-642External Control of Critical State Data
- CWE-643Improper Neutralization of Data within XPath Expressions
- CWE-644Improper Neutralization of HTTP Headers for Scripting Syntax
- CWE-646Reliance on File Name or Extension of Externally-Supplied File
- CWE-647Use of Non-Canonical URL Paths for Authorization Decisions
- CWE-648Incorrect Use of Privileged APIs
- CWE-649Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking
- CWE-650Trusting HTTP Permission Methods on the Server Side
- CWE-651Exposure of WSDL File Containing Sensitive Information
- CWE-652Improper Neutralization of Data within XQuery Expressions
- CWE-653Improper Isolation or Compartmentalization
- CWE-654Reliance on a Single Factor in a Security Decision
- CWE-656Reliance on Security Through Obscurity
- CWE-662Improper Synchronization
- CWE-663Use of a Non-reentrant Function in a Concurrent Context
- CWE-665Improper Initialization
- CWE-666Operation on Resource in Wrong Phase of Lifetime
- CWE-667Improper Locking
- CWE-668Exposure of Resource to Wrong Sphere
- CWE-672Operation on a Resource after Expiration or Release
- CWE-674Uncontrolled Recursion
- CWE-675Multiple Operations on Resource in Single-Operation Context
- CWE-676Use of Potentially Dangerous Function
- CWE-680Integer Overflow to Buffer Overflow
- CWE-681Incorrect Conversion between Numeric Types
- CWE-682Incorrect Calculation
- CWE-685Function Call With Incorrect Number of Arguments
- CWE-688Function Call With Incorrect Variable or Reference as Argument
- CWE-690Unchecked Return Value to NULL Pointer Dereference
- CWE-691Insufficient Control Flow Management
- CWE-697Incorrect Comparison
- CWE-703Improper Check or Handling of Exceptional Conditions
- CWE-704Incorrect Type Conversion or Cast
- CWE-705Incorrect Control Flow Scoping
- CWE-732Incorrect Permission Assignment for Critical Resource
- CWE-733Compiler Optimization Removal or Modification of Security-critical Code
- CWE-749Exposed Dangerous Method or Function
- CWE-754Improper Check for Unusual or Exceptional Conditions
- CWE-755Improper Handling of Exceptional Conditions
- CWE-757Selection of Less-Secure Algorithm During Negotiation
- CWE-759Use of a One-Way Hash without a Salt
- CWE-760Use of a One-Way Hash with a Predictable Salt
- CWE-761Free of Pointer not at Start of Buffer
- CWE-762Mismatched Memory Management Routines
- CWE-763Release of Invalid Pointer or Reference
- CWE-764Multiple Locks of a Critical Resource
- CWE-765Multiple Unlocks of a Critical Resource
- CWE-766Critical Data Element Declared Public
- CWE-768Incorrect Short Circuit Evaluation
- CWE-770Missing resource limits
- CWE-771Missing Reference to Active Allocated Resource
- CWE-772Missing Release of Resource after Effective Lifetime
- CWE-773Missing Reference to Active File Descriptor or Handle
- CWE-774Allocation of File Descriptors or Handles Without Limits or Throttling
- CWE-775Missing Release of File Descriptor or Handle after Effective Lifetime
- CWE-776Improper Restriction of Recursive Entity References in DTDs
- CWE-777Regular Expression without Anchors
- CWE-778Insufficient Logging
- CWE-779Logging of Excessive Data
- CWE-781Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code
- CWE-782Exposed IOCTL with Insufficient Access Control
- CWE-783Operator Precedence Logic Error
- CWE-784Reliance on Cookies without Validation and Integrity Checking in a Security Decision
- CWE-786Access of Memory Location Before Start of Buffer
- CWE-787Out-of-bounds write
- CWE-788Access of Memory Location After End of Buffer
- CWE-789Memory Allocation with Excessive Size Value
- CWE-798Hard-coded credentials
- CWE-805Buffer Access with Incorrect Length Value
- CWE-806Buffer Access Using Size of Source Buffer
- CWE-807Reliance on Untrusted Inputs in a Security Decision
- CWE-822Untrusted Pointer Dereference
- CWE-823Use of Out-of-range Pointer Offset
- CWE-824Access of Uninitialized Pointer
- CWE-825Expired Pointer Dereference
- CWE-826Premature Release of Resource During Expected Lifetime
- CWE-827Improper Control of Document Type Definition
- CWE-828Signal Handler with Functionality that is not Asynchronous-Safe
- CWE-829Untrusted third-party code inclusion
- CWE-831Signal Handler Function Associated with Multiple Signals
- CWE-832Unlock of a Resource that is not Locked
- CWE-833Deadlock
- CWE-834Excessive Iteration
- CWE-835Loop with Unreachable Exit Condition
- CWE-837Improper Enforcement of a Single, Unique Action
- CWE-838Inappropriate Encoding for Output Context
- CWE-839Numeric Range Comparison Without Minimum Check
- CWE-841Improper Enforcement of Behavioral Workflow
- CWE-843Access of Resource Using Incompatible Type
- CWE-862Missing authorization
- CWE-863Incorrect authorization
- CWE-908Use of Uninitialized Resource
- CWE-909Missing Initialization of Resource
- CWE-911Improper Update of Reference Count
- CWE-912Hidden Functionality
- CWE-913Improper Control of Dynamically-Managed Code Resources
- CWE-915Mass assignment
- CWE-916Use of Password Hash With Insufficient Computational Effort
- CWE-917Improper Neutralization of Special Elements used in an Expression Language Statement
- CWE-918Server-side request forgery (SSRF)
- CWE-920Improper Restriction of Power Consumption
- CWE-921Storage of Sensitive Data in a Mechanism without Access Control
- CWE-923Improper Restriction of Communication Channel to Intended Endpoints
- CWE-925Improper Verification of Intent by Broadcast Receiver
- CWE-926Improper Export of Android Application Components
- CWE-927Use of Implicit Intent for Sensitive Communication
- CWE-939Improper Authorization in Handler for Custom URL Scheme
- CWE-940Improper Verification of Source of a Communication Channel
- CWE-941Incorrectly Specified Destination in a Communication Channel
- CWE-942Permissive cross-domain policy (CORS)
- CWE-943Improper Neutralization of Special Elements in Data Query Logic
- CWE-1004Cookie missing HttpOnly flag
- CWE-1007Insufficient Visual Distinction of Homoglyphs Presented to User
- CWE-1021Clickjacking (UI redressing)
- CWE-1022Use of Web Link to Untrusted Target with window.opener Access
- CWE-1037Processor Optimization Removal or Modification of Security-critical Code
- CWE-1039Inadequate Detection or Handling of Adversarial Input Perturbations in Automated Recognition Mechanism
- CWE-1041Use of Redundant Code
- CWE-1046Creation of Immutable Text Using String Concatenation
- CWE-1047Modules with Circular Dependencies
- CWE-1054Invocation of a Control Element at an Unnecessarily Deep Horizontal Layer
- CWE-1059Insufficient Technical Documentation
- CWE-1061Insufficient Encapsulation
- CWE-1069Empty Exception Block
- CWE-1083Data Access from Outside Expected Data Manager Component
- CWE-1088Synchronous Access of Remote Resource without Timeout
- CWE-1102Reliance on Machine-Dependent Data Representation
- CWE-1104Unmaintained third-party components
- CWE-1114Inappropriate Whitespace Style
- CWE-1115Source Code Element without Standard Prologue
- CWE-1116Inaccurate Source Code Comments
- CWE-1164Irrelevant Code
- CWE-1173Improper Use of Validation Framework
- CWE-1177Use of Prohibited Code
- CWE-1188Initialization of a Resource with an Insecure Default
- CWE-1189Improper Isolation of Shared Resources on System-on-a-Chip
- CWE-1191On-Chip Debug and Test Interface With Improper Access Control
- CWE-1204Generation of Weak Initialization Vector
- CWE-1220Insufficient Granularity of Access Control
- CWE-1221Incorrect Register Defaults or Module Parameters
- CWE-1222Insufficient Granularity of Address Regions Protected by Register Locks
- CWE-1223Race Condition for Write-Once Attributes
- CWE-1231Improper Prevention of Lock Bit Modification
- CWE-1233Security-Sensitive Hardware Controls with Missing Lock Bit Protection
- CWE-1235Incorrect Use of Autoboxing and Unboxing for Performance Critical Operations
- CWE-1236Improper Neutralization of Formula Elements in a CSV File
- CWE-1240Use of a Cryptographic Primitive with a Risky Implementation
- CWE-1244Internal Asset Exposed to Unsafe Debug Access Level or State
- CWE-1245Improper Finite State Machines (FSMs) in Hardware Logic
- CWE-1247Improper Protection Against Voltage and Clock Glitches
- CWE-1248Semiconductor Defects in Hardware Logic with Security-Sensitive Implications
- CWE-1249Application-Level Admin Tool with Inconsistent View of Underlying Operating System
- CWE-1250Improper Preservation of Consistency Between Independent Representations of Shared State
- CWE-1251Mirrored Regions with Different Values
- CWE-1254Incorrect Comparison Logic Granularity
- CWE-1255Comparison Logic is Vulnerable to Power Side-Channel Attacks
- CWE-1256Improper Restriction of Software Interfaces to Hardware Features
- CWE-1257Improper Access Control Applied to Mirrored or Aliased Memory Regions
- CWE-1260Improper Handling of Overlap Between Protected Memory Ranges
- CWE-1261Improper Handling of Single Event Upsets
- CWE-1262Improper Access Control for Register Interface
- CWE-1263Improper Physical Access Control
- CWE-1264Hardware Logic with Insecure De-Synchronization between Control and Data Channels
- CWE-1265Unintended Reentrant Invocation of Non-reentrant Code Via Nested Calls
- CWE-1266Improper Scrubbing of Sensitive Data from Decommissioned Device
- CWE-1269Product Released in Non-Release Configuration
- CWE-1270Generation of Incorrect Security Tokens
- CWE-1272Sensitive Information Uncleared Before Debug/Power State Transition
- CWE-1273Device Unlock Credential Sharing
- CWE-1274Improper Access Control for Volatile Memory Containing Boot Code
- CWE-1275Sensitive Cookie with Improper SameSite Attribute
- CWE-1277Firmware Not Updateable
- CWE-1278Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques
- CWE-1281Sequence of Processor Instructions Leads to Unexpected Behavior
- CWE-1284Improper Validation of Specified Quantity in Input
- CWE-1285Improper Validation of Specified Index, Position, or Offset in Input
- CWE-1286Improper Validation of Syntactic Correctness of Input
- CWE-1287Improper Validation of Specified Type of Input
- CWE-1288Improper Validation of Consistency within Input
- CWE-1289Improper Validation of Unsafe Equivalence in Input
- CWE-1291Public Key Re-Use for Signing both Debug and Production Code
- CWE-1293Missing Source Correlation of Multiple Independent Data
- CWE-1295Debug Messages Revealing Unnecessary Information
- CWE-1296Incorrect Chaining or Granularity of Debug Components
- CWE-1297Unprotected Confidential Information on Device is Accessible by OSAT Vendors
- CWE-1298Hardware Logic Contains Race Conditions
- CWE-1299Missing Protection Mechanism for Alternate Hardware Interface
- CWE-1300Improper Protection of Physical Side Channels
- CWE-1301Insufficient or Incomplete Data Removal within Hardware Component
- CWE-1303Non-Transparent Sharing of Microarchitectural Resources
- CWE-1304Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation
- CWE-1310Missing Ability to Patch ROM Code
- CWE-1312Missing Protection for Mirrored Regions in On-Chip Fabric Firewall
- CWE-1313Hardware Allows Activation of Test or Debug Logic at Runtime
- CWE-1314Missing Write Protection for Parametric Data Values
- CWE-1315Improper Setting of Bus Controlling Capability in Fabric End-point
- CWE-1316Fabric-Address Map Allows Programming of Unwarranted Overlaps of Protected and Unprotected Ranges
- CWE-1317Improper Access Control in Fabric Bridge
- CWE-1318Missing Support for Security Features in On-chip Fabrics or Buses
- CWE-1319Improper Protection against Electromagnetic Fault Injection
- CWE-1321Prototype pollution
- CWE-1322Use of Blocking Code in Single-threaded, Non-blocking Context
- CWE-1325Improperly Controlled Sequential Memory Allocation
- CWE-1328Security Version Number Mutable to Older Versions
- CWE-1329Reliance on Component That is Not Updateable
- CWE-1330Remanent Data Readable after Memory Erase
- CWE-1331Improper Isolation of Shared Resources in Network On Chip
- CWE-1332Improper Handling of Faults that Lead to Instruction Skips
- CWE-1333Inefficient Regular Expression Complexity
- CWE-1335Incorrect Bitwise Shift of Integer
- CWE-1336Improper Neutralization of Special Elements Used in a Template Engine
- CWE-1338Improper Protections Against Hardware Overheating
- CWE-1339Insufficient Precision or Accuracy of a Real Number
- CWE-1341Multiple Releases of Same Resource or Handle
- CWE-1342Information Exposure through Microarchitectural State after Transient Execution
- CWE-1357Reliance on Insufficiently Trustworthy Component
- CWE-1385Missing Origin Validation in WebSockets
- CWE-1386Insecure Operation on Windows Junction / Mount Point
- CWE-1389Incorrect Parsing of Numbers with Different Radices
- CWE-1390Weak Authentication
- CWE-1391Use of Weak Credentials
- CWE-1393Use of Default Password
- CWE-1395Dependency on Vulnerable Third-Party Component
- CWE-1419Incorrect Initialization of Resource
- CWE-1420Exposure of Sensitive Information during Transient Execution
- CWE-1421Exposure of Sensitive Information in Shared Microarchitectural Structures during Transient Execution
- CWE-1422Exposure of Sensitive Information caused by Incorrect Data Forwarding during Transient Execution
- CWE-1423Exposure of Sensitive Information caused by Shared Microarchitectural Predictor State that Influences Transient Execution
- CWE-1426Improper Validation of Generative AI Output
- CWE-1427Improper Neutralization of Input Used for LLM Prompting
- CWE-1428Reliance on HTTP instead of HTTPS
- CWE-1429Missing Security-Relevant Feedback for Unexecuted Operations in Hardware Interface
- CWE-1431Driving Intermediate Cryptographic State/Results to Hardware Module Outputs
- CWE-1434Insecure Setting of Generative AI/ML Model Inference Parameters
- CWE-1461Hardware Simulation / Synthesis Mismatch
- CWE-1463Insufficient Session Timeout Value
- CWE-1465Improper Session Invalidation after User Logout
- CWE-1466Improper Session Invalidation after Authentication Credential Change
- CWE-1467Use of Singular Authentication Artifact for Multiple User Sessions
- CWE-1469Improper Check for Credential Expiration
- CWE-1472Generation of Credential with Long Expiration
- CWE-1473Improper Expiration of Cached Data
- CWE-1474Non-Equivalent Data Transformation
- CWE-1475Incomplete Data/State Propagation
- CWE-1476Improper Request Propagation before Data Reception in Write Transactions in a Bus Architecture
No weakness matches that search.
FAQ
CWE: FAQs
Straight answers to what buyers ask us most. Still unsure? Book a free 30-minute call.
What is CWE?
CWE, the Common Weakness Enumeration, is a community-developed list of software and hardware weakness types maintained by MITRE. Each entry describes a kind of mistake in design or code, such as cross-site scripting or missing authorization, that can lead to a security vulnerability if it is not fixed.
What is the difference between CWE and CVE?
A CWE is a type of weakness, such as SQL injection. A CVE is one specific vulnerability found in one specific product, such as an SQL injection flaw in a particular plugin version. Security reports usually give a CVE for the flaw and a CWE for the underlying cause.
Why does a CWE number appear in my security report?
Scanners, penetration testers and vulnerability databases label each finding with the CWE that explains its root cause. The number tells your developer what kind of mistake to look for and which fixes apply, so the same problem can be removed everywhere it occurs, not only where it was found.
How do I know which weaknesses affect my website?
You find out by testing. Automated scanners catch common issues, and a manual review or penetration test finds logic and access-control flaws that tools miss. Keeping the CMS, plugins and libraries updated removes many known weaknesses before anyone can use them.
Is this directory the official CWE list?
No. The official list is published by MITRE at cwe.mitre.org. This directory presents the public CWE data in a readable layout and adds plain-English guidance for the weaknesses that matter most to websites, stores and apps.
Free security review
Not sure where your site is exposed?
Send your URL. A senior engineer reviews it for the most common weaknesses and replies within one business day.
- 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
- Emailhello@codefreex.com
- CallUSA +1 (209) 375-3475 · India +91 790 3375 530
- Prefer to talk?Book a 30-minute call
Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, dated 2026-10-28, 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.