Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-110765 – Authentication Bypass (QuickBooks Webhook Signature Verification) – FlexPrice thro

Be the first to know when new zero-days emerge:

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: HandleQuickBooksWebhook skips signature verification when the intuit-signature header 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-signature header. 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-signature header or allowing only Intuit sources. If QuickBooks payment inbound sync is not needed, disable it. Review recent payment and invoice records for unexpected reconciliations.

References

Get a free Attack Surface scan to see if you’re exposed.

Get a free Attack Surface scan to see if you’re exposed.

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge