dbcve.org
Btcpay ServerApplication · Btcpayserver

CVE-2022-32984

HIGH · 7.5 CVSS v3.1 Published 2023-01-31
Fix available
A fix is available. Upgrade to after 1.5.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
BTCPay Server 1.3.0 through 1.5.3 allows a remote attacker to obtain sensitive information when a public Point of Sale app is exposed. The sensitive information, found in the HTML source code, includes the xpub of the store. Also, if the store isn't using the internal lightning node, the credentials of a lightning node are exposed.

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 confidence

BTCPay Server versions 1.3.0 through 1.5.3 contain an information disclosure vulnerability in the public Point of Sale app. When the POS app is exposed publicly, the HTML source code of the payment page includes the store's xpub (extended public key for wallet derivation) and, if an external lightning node is configured, its credentials. This allows a remote attacker to obtain sensitive cryptographic material and authentication credentials by viewing the page source.

MitigationUpdate BTCPay Server to version 1.5.4 or later to remediate the vulnerability. Additionally, rotate any exposed lightning node credentials and review wallet derivations associated with the exposed xpub, as the internal lightning node may also be affected.

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
Btcpay ServerApplication
Affected:>= 1.3.0, <= 1.5.3

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed BTCPay Server version
    Access the BTCPay Server administration interface and navigate to Server Settings > Maintenance, or check the Docker container/logs for the version number
    Affected if Version is 1.3.0, 1.4.x, or 1.5.0 through 1.5.3
  2. Verify POS app is enabled
    Log into BTCPay Server as a store administrator, go to Plugins > Point of Sale, and confirm the POS app is installed and active for at least one store
    Affected if POS app is installed and enabled for a store
  3. Confirm POS app is publicly accessible
    Access the public POS URL (typically /plugins/pos-{ GUID }) from an external network or confirm the store settings allow unauthenticated public access to the POS app
    Affected if POS app is accessible without authentication to the public internet
  4. Inspect HTML source for exposed xpub
    Visit the public POS payment page, view the page source (right-click > View Page Source or Ctrl+U), and search for strings containing 'xpub' or 'ExtendedPublicKey'
    Affected if The HTML source contains a value resembling an xpub (starts with xpub or zpub and is 100+ characters)
  5. Inspect HTML source for lightning credentials
    In the same page source, search for 'lndgrd', 'lndhub', 'macaroon', or connection strings containing lightning node credentials
    Affected if The HTML source contains base64-encoded macaroons, LND REST credentials, or lightning connection strings

A user is affected if running BTCPay Server 1.3.0-1.5.3 with the POS app publicly accessible and the page source reveals an xpub key or lightning node credentials in the HTML.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.5.3
Interim mitigation

Update BTCPay Server to version 1.5.4 or later to remediate the vulnerability. Additionally, rotate any exposed lightning node credentials and review wallet derivations associated with the exposed xpub, as the internal lightning node may also be affected.

Recommended fix Moderate confidence

BTCPay Server 1.5.4 or later (preferably latest stable 1.6.x or newer)

  1. 1. Review the BTCPay Server release notes at blog.btcpayserver.org for the 1.5.4 or later releases to understand the security fix
  2. 2. Back up your BTCPay Server database and configuration before upgrading
  3. 3. Upgrade BTCPay Server to version 1.5.4 or a later stable release (1.6.0 or newer recommended)
  4. 4. After upgrading, verify that the Point of Sale app no longer exposes sensitive information in HTML source code
  5. 5. If using external lightning nodes, regenerate credentials to ensure compromised credentials are rotated
Caveat Review release notes for potential breaking changes between 1.5.x and later versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Btcpay Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32984 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-32984 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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