Hugo Blog: Unauthenticated AI Proxy Allows Abuse of Server-Side API Key
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| lanshi17 | hugo_blog | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Lanshi17 | Hugo Blog |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.317% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Lanshi17
Lanshi17 hugo Blog |
|
| Vendors & Products |
Lanshi17
Lanshi17 hugo Blog |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Hugo Blog is a tech blog site. In commit 744ca15 and prior, the AI assistant proxy exposes three HTTP endpoints (POST /api/blog-assistant, POST /api/blog-search-embedding, POST /api/blog-search-rerank) without any authentication check. When deployed following the documented Nginx reverse-proxy setup, any unauthenticated remote attacker can send arbitrary requests that the proxy forwards to the upstream LLM/embedding/rerank API using the operator's server-side API key (OPENAI_API_KEY / AI_SEARCH_API_KEY). This enables unlimited quota consumption, cost exhaustion, and potential service unavailability for the operator. At time of publication, there are no publicly available patches. | |
| Title | Hugo Blog: Unauthenticated AI Proxy Allows Abuse of Server-Side API Key | |
| Weaknesses | CWE-306 | |
| References |
| |
| Metrics |
cvssV3_1
|