Summary
CVE-2026-110765 is an authentication bypass (CWE-347, Improper Verification of Cryptographic Signature) in the QuickBooks webhook handler of FlexPrice through version 2.1.38. An unauthenticated remote attacker can submit forged QuickBooks payment notifications and manipulate payment and invoice records. The CVE record carries a CVSS v4.0 score of 8.2 (High).
Technical details
- Root cause:
HandleQuickBooksWebhookskips signature verification when theintuit-signatureheader is omitted. The public researcher write-up also reports that the webhook route has no authentication middleware. It also reports that the verifier accepts any payload when no webhook verifier token is configured for the environment. - Trigger conditions: The attacker needs the target’s tenant ID and environment ID. The write-up also says the attacker needs a QuickBooks realm ID and payment ID for the connected company, and that the target must have a QuickBooks connection with payment inbound sync enabled.
- Attack vector: Network. The attacker sends a forged webhook request with no
intuit-signatureheader. Alternatively, the attacker sends any signature value to an environment that has no verifier token configured. No credentials are required. - Impact: Forged payment events can trigger payment reconciliation. This can alter local payment records and invoice status, for example marking invoices as paid or reconciled without a genuine payment. The CVSS vectors rate this as an integrity impact only.
Affected software
- FlexPrice (github.com/flexprice/flexprice) versions 0 through 2.1.38
Severity
- CVSS v4.0: 8.2 (High),
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N - CVSS v3.1: 5.9 (Medium),
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Mitigation and recommended actions
- Immediate: I found no fixed release in the sources I reviewed. The researcher write-up said none existed when it was published. Check the FlexPrice repository for a release later than 2.1.38 before you rely on this.
- Remediation the write-up describes: reject unsigned requests (a missing header should return 401), and treat an empty verifier token as a configuration error instead of accepting the request.
- Workarounds: Configure a QuickBooks webhook verifier token in every environment. Restrict access to the QuickBooks webhook endpoint at the network or reverse-proxy level, for example by requiring the
intuit-signatureheader or allowing only Intuit sources. If QuickBooks payment inbound sync is not needed, disable it. Review recent payment and invoice records for unexpected reconciliations.

