SerpBear before 3.1.1 Missing Authentication via POST /api/notify
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| towfiqi | serpbear | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Towfiqi | Serpbear |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.626% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Towfiqi
Towfiqi serpbear |
|
| Vendors & Products |
Towfiqi
Towfiqi serpbear |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | SerpBear before 3.1.1 contains a missing authentication vulnerability in pages/api/notify.ts that allows remote unauthenticated attackers to trigger notification emails because verifyUser() is never called. Attackers can repeatedly POST to /api/notify, optionally with a domain parameter, to exhaust SMTP rate limits, trigger provider abuse flags and flood recipients. | |
| Title | SerpBear before 3.1.1 Missing Authentication via POST /api/notify | |
| Weaknesses | CWE-306 | |
| References |
|
|
| Metrics |
cvssV3_1
|