SerpBear before 3.1.1 Missing Authentication via POST /api/notify
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.1.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
SerpBear, a self-hosted search engine rank tracking application, is affected in this vulnerability. An unauthenticated remote attacker can repeatedly trigger its notification endpoint to send emails, which can exhaust the mail server's sending limits, cause the email provider to flag the account for abuse, and flood recipients with unwanted messages.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- towfiqi serpbear
fixed in 3.1.1