Security Resilience

CWE · MITRE source

CWE-393Return of Wrong Status Code

Abstraction: Base · CVEs in our corpus: 15

A function or operation returns an incorrect return value or status code that does not indicate the true result of execution, causing the product to modify its behavior based on the incorrect result.

This can lead to unpredictable behavior. If the function is used to make security-critical decisions or provide security-critical information, then the wrong status code can cause the product to assume that an action is safe or correct, even when it is not.

Last updated: 14 October 2026 20:41 UTC

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • PR.PS-06
  • SA-11 Developer Testing and Evaluation
  • SI-6 Security and Privacy Function Verification
Detect
Catch it (CSF Detect / Respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted

These are model PROPOSALS, not graded mappings. They come from controls_to_cwe_proposals, which carries no grade field at all; across the CWE pages 1,540 of 1,722 such associations (89%) have never been graded by anything. The heading said “address” until 2026-09-29, which asserted a relationship the data does not carry. Graded cross-walks are on the framework map, not here.

Control Title Family Why it addresses this CWE
No NIST controls proposed yet.

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2026-973816.89.90.00212026-10-13
CVE-2025-5987 6.58.10.01732025-07-07
CVE-2024-49117 6.48.80.01032024-12-12
CVE-2023-37897 5.97.20.02812023-07-18
CVE-2026-559585.87.50.00442026-06-25
CVE-2026-42246 5.67.40.00312026-05-09
CVE-2026-53092 5.67.80.00132026-06-24
CVE-2026-928215.26.80.00312026-10-06
CVE-2025-24531 5.06.70.00232026-01-16
CVE-2020-5401 4.75.30.01042020-02-27
CVE-2025-32414 4.25.60.00382025-04-08