CVE-2021-29251 json
BTCPay Server before 1.0.7.1 mishandles the policy setting in which users can register (in Server Settings > Policies).
published 5y ago modified 4mo ago also EUVD-2021-15890
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
BTCPay Server before 1.0.7.1 mishandles the policy setting in which users can register (in Server Settings > Policies). This affects Docker use cases in which a mail server is configured.
Patch / fix
- btcpayserver btcpay_server 1.0.7.1
Is CVE-2021-29251 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
References
-
blog.btcpayserver.org
/vulnerability-disclosure-v1-0-7-0/
release-notes, vendor-advisory
-
github.com
/btcpayserver/btcpayserver/releases/tag/v1.0.7.1
release-notes, third-party-advisory
Sources
- CVE List CVE-2021-29251
- NVD CVE-2021-29251
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.