Exploit for cve-lab-journal

## https://sploitus.com/exploit?id=45C77830-4019-5D84-933F-72D69EF09468
# CVE Lab Journal

![CVEs logged](https://img.shields.io/badge/CVEs%20logged-1-blue)
![Last updated](https://img.shields.io/badge/last%20updated-2026--08--19-informational)
![Scope](https://img.shields.io/badge/scope-authorized%20local%20lab%20only-success)
![Focus](https://img.shields.io/badge/focus-defensive%20%2F%20educational-important)

A running log of daily CVE analysis drills — reading the advisory, finding the actual patch commit, building a proof-of-concept, standing up a vulnerable environment in Docker, and confirming the exploit works (and that the patch fixes it). Purely for hands-on learning: every target here is a container running on `127.0.0.1`, never a real system.

## Why this exists

Reading a CVE description isn't the same as understanding it. This repo is the practice log for a repeatable process:

1. **Read** the NVD entry and vendor advisory in full
2. **Find** the actual patch commit — what line of code was the bug, really
3. **Build or find** a PoC
4. **Stand up** a vulnerable version locally (Docker)
5. **Run** the exploit, confirm it works, confirm the patched version blocks it, understand *why*
6. **Check** whether it's relevant to anything self-hosted

## Log

| Date | CVE | CVSS | Software | Bug class | Status |
|---|---|---|---|---|---|
| 2026-08-19 | [CVE-2026-73056](entries/CVE-2026-73056/) | 9.8 Critical | SiYuan (self-hosted notes) | CWE-307 — missing auth throttle | Reproduced + patch verified |

## Structure

Each entry lives in `entries//` and follows [`entries/TEMPLATE.md`](entries/TEMPLATE.md) — advisory summary, the real patch diff, the PoC script used, and the before/after results of running it against vulnerable vs. patched builds.

## Disclaimer

Everything here is run against software the author controls, in isolated Docker containers, for personal skill-building. Nothing in this repo targets or was tested against third-party systems.