CWE · MITRE source
CWE-283Unverified Ownership
The product does not properly verify that a critical resource is owned by the proper entity.
Last updated: 16 October 2026 14:24 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 2 mapping(s) from 2 framework(s): STIG windows server 2016 1 (partial) · STIG windows server 2019 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A01:2025 Broken Access Control.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
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-2024-27903 UPD | 8.1 | 9.8 | 0.0892 | 2024-07-08 |
CVE-2026-20912 UPD | 6.9 | 9.1 | 0.0046 | 2026-01-22 |
CVE-2021-24501 UPD | 6.4 | 8.1 | 0.0125 | 2021-08-09 |
CVE-2021-24500 UPD | 6.2 | 8.1 | 0.0065 | 2021-08-09 |
CVE-2026-85781 | 6.2 | 8.7 | 0.0044 | 2026-09-04 |
CVE-2026-26016 | 6.1 | 8.1 | 0.0047 | 2026-02-19 |
CVE-2020-8554 UPD | 5.8 | 6.3 | 0.0927 | 2021-01-21 |
CVE-2026-29788 | 5.8 | 7.5 | 0.0037 | 2026-03-06 |
CVE-2026-83791 | 5.8 | 7.8 | 0.0028 | 2026-10-13 |
CVE-2026-4269 UPD | 5.7 | 7.5 | 0.0043 | 2026-03-16 |
CVE-2025-43882 UPD | 5.6 | 7.8 | 0.0013 | 2025-08-27 |
CVE-2025-47940 UPD | 5.4 | 7.2 | 0.0046 | 2025-05-20 |
CVE-2026-44707 UPD | 5.3 | 6.8 | 0.0046 | 2026-05-26 |
CVE-2026-110237 | 5.3 | 7.3 | 0.0015 | 2026-10-13 |
CVE-2022-29220 UPD | 5.1 | 6.5 | 0.0049 | 2022-05-31 |
CVE-2026-9745 | 5.1 | 6.5 | 0.0032 | 2026-09-03 |
CVE-2026-44562 UPD | 5.0 | 6.5 | 0.0035 | 2026-05-15 |
CVE-2025-24890 UPD | 5.0 | 6.8 | 0.0019 | 2026-09-14 |
CVE-2026-54467 UPD | 4.8 | 7.0 | 0.0017 | 2026-08-26 |
CVE-2026-87912 | 4.6 | 5.9 | 0.0044 | 2026-09-10 |
CVE-2026-87913 | 4.6 | 5.9 | 0.0044 | 2026-09-10 |
CVE-2025-1007 UPD | 4.5 | 5.3 | 0.0052 | 2025-02-19 |
CVE-2026-27486 | 4.4 | 5.3 | 0.0038 | 2026-02-21 |
CVE-2024-1853 UPD | 4.2 | 5.5 | 0.0020 | 2024-03-14 |
CVE-2025-9822 UPD | 4.2 | 5.5 | 0.0024 | 2025-09-03 |