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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.9 · towfiqiNVD modified 2026-10-30 15:16
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 6
- https://github.com/towfiqi/serpbear/issues/359 issue-tracking
- https://github.com/towfiqi/serpbear product
- https://github.com/towfiqi/serpbear/commit/12dc0a4bd91f06de2dab96f797c495942f7ef8c9 patch
- https://github.com/towfiqi/serpbear/blob/v3.1.0/pages/api/notify.ts#L16-L21 technical-description
- https://github.com/towfiqi/serpbear/releases/tag/v3.1.1 release-notes
- https://www.vulncheck.com/advisories/serpbear-before-3.1.1-missing-authentication-via-post-api-notify third-party-advisory