Stored HTML injection via raw payment metadata rendering
Published Mar 2, 2023 · Updated Mar 7, 2025
Stored HTML injection in BTCPay Server before 1.8.0 allows remote authenticated users to render crafted markup in another user's browser. Razor views pass payment request, posData, receiptData, and related payment values through Safe.Raw instead of contextual encoding. Reachability requires an authenticated user to store crafted payment metadata and another user to open an affected view.
Summary
What happened
Stored HTML injection in BTCPay Server before 1.8.0 allows remote authenticated users to render crafted markup in another user's browser. Razor views pass payment request, posData, receiptData, and related payment values through Safe.Raw instead of contextual encoding. Reachability requires an authenticated user to store crafted payment metadata and another user to open an affected view.
The record
- CVE
- CVE-2023-1149
- Published
- Mar 2, 2023
- Updated
- Mar 7, 2025
- Vendor
- BTCPay Server
- Product
- BTCPay Server
- Classifications
- CWE-76, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 2, 2023CVE publishedPublication date reported by the CVE source.
- Mar 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <1.8.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- huntr.dev HTML injection proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo