CVE-2023-1149
Btcpayserver Btcpay Server ≤ 1.8.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-1149 is a medium-severity Improper Neutralization of Equivalent Special Elements (CWE-76) vulnerability in Btcpayserver Btcpay Server. Its CVSS base score is 5.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked at the 45th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-23432
Vulnerability Data
Improper Neutralization of Equivalent Special Elements in GitHub repository btcpayserver/btcpayserver prior to 1.8.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require consistent neutralization of all equivalent special elements during input validation and sanitization.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.8.25 mandates secure SDLC practices (secure coding guidelines, security requirements, checkpoints, testing, developer training) that reach improper neutralization of equivalent special elements, but only as one slice of a broad requirement whose implementation scope and rigour are left to the organisation.
Application security requirements include rules for handling special characters and equivalent encodings.
A.8.27 mandates security-by-design principles (defense-in-depth, least privilege, distrust external input, fail securely, hardening, design review against attack patterns) that reach some but not most cases of equivalent-special-element neutralization failures.
Secure coding standards directly address proper neutralization of all equivalent special elements.
Security testing can detect incomplete neutralization but does not prevent the weakness itself.