| Advisory / CVE | Product | Vulnerability & Weakness | Severity | Status |
|---|---|---|---|---|
| GHSA-fc85-99vc-9c75 | Knowns | CWE-284 & CWE-306 & CWE-1188 | Published (CVE Accepted - waiting for GHSA) | |
| GHSA-3h35-4jq7-hv45 | Knowns | CWE-20 & CWE-22 & CWE-284 & CWE-732 | Published (CVE Accepted - waiting for GHSA) | |
| GHSA-f539-xgc6-xw7q | Knowns | CWE-22 & CWE-73 & CWE-863 | Published (CVE Accepted - waiting for GHSA) | |
| GHSA-wh3c-v55g-qfg8 | Knowns | CWE-22 & CWE-73 & CWE-78 & CWE-94 & CWE-306 | Published (CVE Accepted - waiting for GHSA) | |
| GHSA-hjr3-7rcc-2hjw | Pending | CWE-345 & CWE-346 & CWE-441 & CWE-601 & CWE-918 | Triage | |
| GHSA-g99m-r8mj-vqmc | Pending | CWE-183 & CWE-319 & CWE-346 & CWE-601 & CWE-918 | CERT/CC submited | |
| GHSA-79x2-993q-xvjq | Pending | CWE-20 & CWE-347 & CWE-358 & CWE-670 | CERT/CC submited | |
| GHSA-25rf-g95j-5c8q | Pending | CWE-20 & CWE-119 & CWE-125 & CWE-295 & CWE-400 & CWE-787 & CWE-789 | Triage | |
| GHSA-5gf4-53wc-3fgw | Pending | CWE-20 & CWE-125 | Triage | |
| GHSA-q5j5-qp67-65vf | Pending | CWE-200 & CWE-863 | Triage | |
| GHSA-rmm7-wqw2-jwc6 | Pending | CWE-441 & CWE-862 & CWE-918 | Triage | |
| GHSA-w323-3wpx-f7g5 | Knowns | CWE-269 & CWE-693 & CWE-863 | Published (CVE Accepted - waiting for GHSA) | |
| GHSA-mc52-mwq4-vfx3 | Knowns | CWE-78 & CWE-94 & CWE-427 & CWE-829 | Published (CVE Accepted - waiting for GHSA) | |
| GHSA-qx9v-m9gg-p5jg | Knowns | CWE-918 & CWE-200 & CWE-306 | Published (CVE Accepted - waiting for GHSA) | |
| GHSA-fpxv-c555-rhm3 | Knowns | CWE-22 & CWE-200 & CWE-306 | Published (CVE Accepted - waiting for GHSA) | |
| GHSA-9gfj-28hw-jchp | Knowns | CWE-22 & CWE-73 & CWE-863 | Published (CVE Accepted - waiting for GHSA) |
i'm uziii2208, also a 0pwn. I'm Co-Owner of @HowToPwn
- Ho Chi Minh City, Vietnam
-
17:28
(UTC +07:00) - 0pwn0.github.io
Pinned Loading
-
CVE-2025-33073
CVE-2025-33073 PublicUniversal exploitation tool for CVE-2025-33073 targeting Windows Domain Controllers with DNSAdmins privileges and WinRM enabled.
Something went wrong, please refresh the page to try again.
If the problem persists, check the GitHub status page or contact support.
If the problem persists, check the GitHub status page or contact support.