CWE · MITRE source
CWE-1385Missing Origin Validation in WebSockets
The product uses a WebSocket, but it does not properly verify that the source of data or communication is valid.
WebSockets provide a bi-directional low latency communication (near real-time) between a client and a server. WebSockets are different than HTTP in that the connections are long-lived, as the channel will remain open until the client or the server is ready to send the message, whereas in HTTP, once the response occurs (which typically happens immediately), the transaction completes. A WebSocket can leverage the existing HTTP protocol over ports 80 and 443, but it is not limited to HTTP. WebSockets can make cross-origin requests that are not restricted by browser-based protection mechanisms such as the Same Origin Policy (SOP) or Cross-Origin Resource Sharing (CORS). Without explicit origin validation, this makes CSRF attacks more powerful.
Last updated: 14 October 2026 20:41 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
PR.AA-03PR.AA-05PR.IR-01PR.PS-06
—
—
V4.4.2
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-23168 UPD | 7.3 | 9.8 | 0.0040 | 2024-08-15 |
CVE-2024-48849 UPD | 7.2 | 9.4 | 0.0092 | 2025-01-29 |
CVE-2025-24964 UPD | 6.8 | 9.6 | 0.0068 | 2025-02-04 |
CVE-2026-44211 UPD | 6.6 | 9.6 | 0.0021 | 2026-06-01 |
CVE-2026-10054 | 6.4 | 8.8 | 0.0022 | 2026-07-03 |
CVE-2026-85183 UPD | 6.4 | 9.3 | 0.0023 | 2026-09-03 |
CVE-2026-71416 UPD | 6.3 | 8.8 | 0.0017 | 2026-09-11 |
CVE-2026-77363 | 6.3 | 8.8 | 0.0016 | 2026-10-12 |
CVE-2023-30856 UPD | 6.0 | 8.3 | 0.0035 | 2023-04-28 |
CVE-2026-59950 | 6.0 | 8.1 | 0.0023 | 2026-07-15 |
CVE-2023-0957 UPD | 5.9 | 8.2 | 0.0041 | 2023-03-03 |
CVE-2025-54289 UPD | 5.9 | 8.1 | 0.0021 | 2025-10-02 |
CVE-2026-34403 | 5.9 | 8.1 | 0.0022 | 2026-04-20 |
CVE-2023-26114 UPD | 5.8 | 8.2 | 0.0034 | 2023-03-23 |
CVE-2026-57111 | 5.8 | 7.5 | 0.0035 | 2026-07-09 |
CVE-2023-2848 UPD | 5.7 | 8.0 | 0.0037 | 2023-09-14 |
CVE-2026-35589 UPD | 5.6 | 8.0 | 0.0020 | 2026-04-14 |
CVE-2025-68930 | 5.5 | 7.1 | 0.0056 | 2026-02-23 |
CVE-2026-59804 UPD | 5.2 | 6.8 | 0.0031 | 2026-07-08 |
CVE-2025-24010 UPD | 5.0 | 6.5 | 0.0029 | 2025-01-20 |
CVE-2026-22689 UPD | 5.0 | 6.5 | 0.0024 | 2026-01-10 |
CVE-2025-56647 UPD | 4.9 | 6.5 | 0.0022 | 2026-02-12 |
CVE-2026-44514 UPD | 4.9 | 6.5 | 0.0019 | 2026-05-14 |
CVE-2025-36116 UPD | 4.8 | 6.3 | 0.0017 | 2025-07-23 |
CVE-2023-49805 UPD | 4.6 | 6.0 | 0.0038 | 2023-12-11 |