OWASP / OWASP/Top10

[A01:2025] Incorrect CWE-201 Name in List of Mapped CWEs

Open Beginner friendly
#930 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
6.1k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

Description:

In the List of Mapped CWEs section, CWE-201 is listed as:

"Exposure of Sensitive Information Through Sent Data"

However, the official name as defined by the CWE dictionary is:

"Insertion of Sensitive Information Into Sent Data"

Reference: https://cwe.mitre.org/data/definitions/201.html

Why It Matters:

The List of Mapped CWEs section is meant to be a precise technical reference that maps directly to the official CWE catalog. Using an incorrect name can cause confusion for developers and security practitioners who cross-reference with the official CWE documentation.

Steps to Reproduce:
  1. Navigate to https://owasp.org/Top10/2025/A01_2025-Broken_Access_Control/
  2. Scroll down to the List of Mapped CWEs section
  3. Observe the name listed for CWE-201
Image Image
Expected Behavior:

CWE-201 should be listed as:

"Insertion of Sensitive Information Into Sent Data"

Actual Behavior:

CWE-201 is listed as:

"Exposure of Sensitive Information Through Sent Data"

Proposed Fix:

Update the CWE-201 entry name to match the official CWE name.

I am willing to submit a PR for this fix. 🙂

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the A01:2025 Broken Access Control page and locate its List of Mapped CWEs section. Update the CWE-201 name to match the official CWE dictionary entry, then review the rendered page to confirm the corrected wording appears in the mapping.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation, security
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.