BaseDraft

CWE-358Improperly Implemented Security Check for Standard

Category: other

Description

The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.

Common consequences· 1

  • Access Control — Bypass Protection Mechanism

References

  1. https://cwe.mitre.org/data/definitions/358.html

(incoming)8

TypeTargetConfidenceTier
VulnerabilityCVE-2025-10457cve-2025-104570%live
VulnerabilityCVE-2025-3069cve-2025-30690%live
VulnerabilityCVE-2025-62002cve-2025-620020%live
VulnerabilityCVE-2025-62583cve-2025-625830%live
VulnerabilityCVE-2025-66603cve-2025-666030%live
VulnerabilityCVE-2025-69234cve-2025-692340%live
VulnerabilityCVE-2026-1486cve-2026-14860%live
KEVEntryGoogle Chromium V8 Inappropriate Implementation Vulnerabilitykev-cve-2024-79650%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Violation of Secure Design Principles
CWE
Use of a Cryptographic Primitive with a Risky Implementation
CWE
Incorrect Implementation of Authentication Algorithm
CWE
Use of a Broken or Risky Cryptographic Algorithm
CWE
Insufficient Verification of Data Authenticity
CWE
Use of Insufficiently Random Values
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.