What CVEs are caused by CWE-710?

6 recorded CVEs are attributed to CWE-710, including CVE-2021-27501, CVE-2021-33528, CVE-2020-1613.

What are the consequences of CWE-710?

Exploiting CWE-710 can lead to: Other.

Is CWE-710 actively exploited?

6 recorded CVEs are caused by CWE-710; none are currently in CISA's KEV catalog of actively exploited flaws.

RadicalNotion.AI

Log in Start free

Log in

Log in Start free

Pillar weakness

Incomplete

CWE-710: Improper Adherence to Coding Standards

The product does not follow certain coding rules for development, which can lead to resultant weaknesses or increase the severity of the associated vulnerabilities.

Last updated May 1, 2026

6

Recorded CVEs

With this primary weakness

0

KEVs

In the CISA KEV catalog

Not rated

Likelihood of exploit

Per MITRE

Pillar

Abstraction

MITRE classification

Overview

CWE-710 (Improper Adherence to Coding Standards) is a pillar-level software weakness catalogued by MITRE in the Common Weakness Enumeration (CWE). It describes a recurring type of mistake that can lead to exploitable security vulnerabilities.

Real-world CVEs

6 recorded CVEs are caused by CWE-710 (Improper Adherence to Coding Standards). The highest-severity and most recent are shown first. 0 new CWE-710 CVEs have been recorded so far in 2026 (1 in 2025).

CVE-2020-1603

High · CVSS 8.6 · EPSS 70th

2020-01-15

CVE-2023-30961

Palantir Gotham UI bug that could lead to incorrect data classification

Medium · CVSS 6.5 · EPSS 27th

2023-09-26

CVE-2025-0007

Medium · CVSS 5.7 · EPSS 1th

2025-11-24

Common consequences

What can happen when CWE-710 is exploited.

Other

Affects: Other

How it happens

When it is introduced

Typically introduced during these phases of the software lifecycle.

Architecture and Design

Implementation

How to prevent it

Practical mitigations for CWE-710, grouped by where in the lifecycle they apply.

Policy

Select and require coding standards. Ensure that they include security concerns.

Implementation

Closely follow coding standards, possibly enforcing them upon checkin of the code into a source control system or with periodic analyses.

How to detect it

Automated Static Analysis

Automated tools can detect violations of many code standards.

Frequently asked questions

Common questions about CWE-710.

What is CWE-710?: The product does not follow certain coding rules for development, which can lead to resultant weaknesses or increase the severity of the associated vulnerabilities.
What CVEs are caused by CWE-710?: 6 recorded CVEs are attributed to CWE-710, including CVE-2021-27501, CVE-2021-33528, CVE-2020-1613.
How do you prevent CWE-710?: Select and require coding standards. Ensure that they include security concerns.
How is CWE-710 detected?: Automated Static Analysis: Automated tools can detect violations of many code standards.
What are the consequences of CWE-710?: Exploiting CWE-710 can lead to: Other.
Is CWE-710 actively exploited?: 6 recorded CVEs are caused by CWE-710; none are currently in CISA's KEV catalog of actively exploited flaws.

References

Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.

Stay ahead of CWE-710

Get alerted the moment a new CWE-710 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.

Start free See pricing