CVE-2023-0493
Btcpayserver Btcpay Server ≤ 1.7.5
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-0493 is a medium-severity Improper Neutralization of Equivalent Special Elements (CWE-76) vulnerability in Btcpayserver Btcpay Server. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked in the top 5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-0493 is an improper neutralization of equivalent special elements vulnerability present in the btcpayserver/btcpayserver GitHub repository prior to version 1.7.5. The flaw is also referenced under CWEs 76 and 74 and carries a CVSS 3.1 base score of 5.3 reflecting network attack vector, low complexity, and no required privileges or user interaction, with impact limited to partial availability loss.
An unauthenticated remote attacker can supply crafted input that is not properly sanitized, resulting in HTML injection that may degrade service availability. Public references explicitly label the issue as HTML injection in BTCPay Server 1.7.4 and earlier.
The referenced GitHub pull request and associated commit neutralize the special elements responsible for the injection. The fix is included in the 1.7.5 release, and the issue was tracked through a huntr.dev bounty submission.
EPSS for the CVE has remained flat at 0.0999 with no material rise after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-0312
Vulnerability Data
Improper Neutralization of Equivalent Special Elements in GitHub repository btcpayserver/btcpayserver prior to 1.7.5.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Developer assessments and testing (including injection-focused techniques) identify improper neutralization of special elements, and the verifiable flaw remediation corrects them pre-deployment.
Identifies indicators of injection attacks (command, SQL, LDAP, etc.) via anomaly and attack monitoring.
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.
Logging supports detection of injection attempts but does not prevent the weakness.
Monitoring activities can identify active injection attacks after they occur.
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.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-74, a class-level weakness, and none of its children carries one either.