CVE-2021-29250
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBTCPay Server through 1.0.7.0 suffers from a Stored Cross Site Scripting (XSS) vulnerability within the POS Add Products functionality. This enables cookie stealing.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBTCPay Server through version 1.0.7.0 contains a stored XSS vulnerability in the Point of Sale (POS) Add Products functionality. Attackers can inject malicious JavaScript into product fields which executes when other users view the POS interface, enabling cookie stealing and session hijacking.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.0.7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify BTCPay Server installationLocate the BTCPay Server instance - typically runs as a Docker container, self-hosted on Linux, or as a Windows service. Check for btcpayserver processes or docker containers named btcpayserver.Affected if BTCPay Server is installed and running
-
Check installed versionAccess the BTCPay Server administration interface, go to Server Settings > Maintenance, or run 'docker ps' to check the container image tag. Verify the exact version number against the affected range (<= 1.0.7.0).Affected if Installed version is 1.0.7.0 or any earlier version
-
Determine if POS feature is enabledNavigate through the BTCPay Server UI to check if Point of Sale (POS) apps have been created. Look for any POS storefronts or apps configured in the server.Affected if POS functionality is actively used or configured on the server
-
Inspect POS product fields for malicious payloadsAccess the POS Add Products interface (Apps > Point of Sale > Products). Examine all product fields including Name, Description, Price, and Custom Fields for suspicious script tags, event handlers (onclick, onload, etc.), or encoded JavaScript patterns.Affected if Any product fields contain unsanitized script tags, JavaScript event handlers, or other XSS payloads that would execute when the POS is viewed
You are affected if running BTCPay Server version 1.0.7.0 or earlier AND the POS feature is enabled with products containing malicious script content in any product fields.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement input validation and output encoding on all product fields in the POS Add Products functionality; sanitize or remove existing malicious payloads from the database.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29250 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-29250 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data