CWE Directory: Software Weaknesses Explained | Codefreex Skip to content

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.

613 weaknesses2025 CWE Top 25CWE version 5.0

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.

01CWE-79

Cross-site scripting (XSS)

Attackers plant scripts in your pages that run in visitors’ browsers and can hijack their sessions or accounts.

02CWE-89

SQL injection (SQLi)

Untrusted input changes your database queries, letting attackers read, alter or delete the data your business runs on.

03CWE-352

Cross-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-862

Missing authorization

Your site performs an action or shows data without checking whether the person asking is allowed to.

05CWE-787

Out-of-bounds write

Software writes data outside the memory it reserved, which can crash it or let attackers run their own code.

06CWE-22

Path traversal

Attackers manipulate a file path your site accepts to read or overwrite files outside the folder you intended.

07CWE-416

Use after free (UAF)

A program keeps using memory after releasing it, which can cause crashes, data leaks or attacker-controlled code execution.

08CWE-125

Out-of-bounds read

Software reads memory outside the area it should, which can leak secrets or crash the program.

09CWE-78

OS command injection

Untrusted input reaches a system command your server runs, letting attackers execute their own commands on it.

10CWE-94

Code injection

Your application builds and runs code from untrusted input, so attackers can make it execute instructions they wrote.

11CWE-120

Classic buffer overflow

A program copies input into a fixed-size memory buffer without checking that it fits, corrupting nearby memory.

12CWE-434

Unrestricted file upload

Your site accepts uploaded files without proper checks, so an attacker can upload a file the server will run.

13CWE-476

Null pointer dereference

A program tries to use a reference that points to nothing, which usually makes it crash or stop responding.

14CWE-121

Stack-based buffer overflow

A program writes past a buffer on its call stack, causing crashes or handing control to an attacker.

15CWE-502

Insecure deserialization

Your application rebuilds objects from data an attacker can modify, which can lead to tampering or code execution.

16CWE-122

Heap-based buffer overflow

A program writes past a dynamically allocated memory block, corrupting nearby data and risking crashes or code execution.

17CWE-863

Incorrect authorization

Your site checks permissions, but the check is flawed, so some users get access they should not have.

18CWE-20

Improper input validation

Your site accepts data without checking it properly, so unexpected values can crash it or corrupt records.

19CWE-284

Broken access control

People can reach pages, data or actions on your site that should be off limits to them.

20CWE-200

Information disclosure

Your site reveals private data or technical details to people who were never meant to see them.

21CWE-306

Missing authentication

An important feature on your site works without a login, so anyone who finds it can use it.

22CWE-918

Server-side request forgery (SSRF)

An attacker tricks your server into fetching addresses of their choosing, including systems only your server can reach.

23CWE-77

Command injection

User input ends up inside a command your server runs, letting an attacker change what that command does.

24CWE-639

Insecure direct object reference (IDOR)

Changing an ID in a link or request lets one user open or edit another user’s records.

25CWE-770

Missing 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.

CWE-209

Verbose error messages

Error pages reveal technical details, such as file paths or database queries, that help an attacker plan.

CWE-269

Improper privilege management

Accounts or programs end up with more power than they should have, or can raise their own access.

CWE-276

Incorrect default permissions

Files, folders or cloud storage are created with access that is far wider than they need.

CWE-287

Broken authentication

Your site accepts someone’s claim about who they are without properly proving it, so attackers can pose as real users.

CWE-307

Missing brute-force protection

Your login accepts unlimited password guesses, so automated tools can keep trying until one works.

CWE-312

Cleartext storage of sensitive data

Sensitive data is stored unencrypted, so anyone who reaches the file or database can simply read it.

CWE-319

Unencrypted data transmission

Sensitive data travels between systems without encryption, so anyone on the network path can read or alter it.

CWE-327

Weak or broken encryption

Your site protects data with an outdated or homemade cryptographic method that a determined attacker may be able to break.

CWE-384

Session fixation

An attacker plants a session ID on a visitor, waits for the login, then takes over the account.

CWE-400

Resource exhaustion (denial of service)

Your site lets one user consume unlimited memory, processing power or storage until it slows down or stops.

CWE-521

Weak password requirements

Your site accepts short, common or previously leaked passwords, which makes customer and admin accounts easy to break into.

CWE-522

Weakly protected credentials

Passwords or login tokens are stored or sent in a way that lets someone else capture and reuse them.

CWE-532

Sensitive data in logs

Passwords, tokens or customer details get written to log files that far more people and systems can read.

CWE-601

Open redirect

A link on your trusted domain can be altered to send visitors to a site an attacker controls.

CWE-611

XML external entity (XXE)

An XML file your server processes can instruct it to read local files or contact other systems.

CWE-614

Cookie missing Secure flag

Login cookies can be sent over unencrypted connections, where others on the same network may capture them.

CWE-640

Weak password reset mechanism

A flawed forgot-password process lets someone take over an account without ever knowing the real password.

CWE-798

Hard-coded credentials

Passwords, API keys or secret keys are written directly into your code, where others can find and reuse them.

CWE-829

Untrusted third-party code inclusion

Your site runs code loaded from a source you do not control, so its problems become yours.

CWE-915

Mass assignment

Your app saves every field a request sends, including ones users should never be allowed to change.

CWE-942

Permissive cross-domain policy (CORS)

Your site’s browser security policy trusts domains it should not, letting other websites read data or run scripts.

CWE-1004

Cookie missing HttpOnly flag

Login cookies can be read by scripts running on the page, so one script flaw can expose sessions.

CWE-1021

Clickjacking (UI redressing)

Another site loads your page in a hidden frame and tricks visitors into clicking things they cannot see.

CWE-1104

Unmaintained third-party components

Your site depends on plugins or libraries nobody maintains, so newly found security flaws never get fixed.

CWE-1321

Prototype 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.

613 weaknesses

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

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.