Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessEnumerate valid tenant and environment ID
-
DeliveryOmit intuit-signature header in webhook request
-
ExploitSkip server-side signature verification
-
ExecutionReplay forged payment notifications
-
ImpactMark invoices paid or overpaid
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
|
| Exploitation Conditions | Exploitation requires the FlexPrice QuickBooks webhook integration (HandleQuickBooksWebhook) to be configured and its endpoint network-reachable, and the attacker must know a valid tenant and environment ID (reflected as AT:P in the CVSS 4.0 vector). The core defect is that omitting the intuit-signature header entirely causes the server to skip signature verification rather than reject the request, so no valid signature or secret is needed. Limiting factors: the requirement to possess or enumerate correct tenant/environment identifiers and the need for QuickBooks billing integration to be in use; deployments not using QuickBooks webhooks are unaffected. No user interaction or authentication is required once the IDs are known. |
| Impact | This is a credible, moderate-to-high integrity risk, but not a drop-everything emergency. The CVSS 4.0 base score of 8.2 is driven entirely by integrity impact (VI:H) with no confidentiality or availability impact (VC:N/VA:N), which matches the described behavior: forged payment notifications corrupt invoice/payment state rather than exposing data or crashing the service. The vector is network-reachable and unauthenticated (AV:N/PR:N/UI:N), lowering the barrier, but it carries AT:P (attack requirement present) because the attacker must first know a valid tenant and environment ID - a genuine gating factor that distinguishes this from a fully trivial AV:N/AC:L/AT:N bug. No EPSS score, KEV listing, or explicit exploit-code flag was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; however, a detailed third-party technical writeup (hackmd) and a VulnCheck advisory exist, which materially lowers the effort to weaponize. The signals are internally consistent - CWE-347 (improper signature verification), the 'Authentication Bypass' tag, and the description all align. The main uncertainty is how guessable/enumerable tenant and environment IDs are in practice; if they are sequential or leak elsewhere, real-world exploitability rises toward the CVSS implication. Prioritize patching for any production FlexPrice deployment using the QuickBooks webhook integration, but this is lower urgency than a KEV-listed RCE. |
| Exploit ScenarioDerived | An attacker who has obtained or guessed a valid tenant and environment ID sends an HTTP POST to the QuickBooks webhook endpoint while deliberately omitting the intuit-signature header, causing FlexPrice to skip signature verification entirely. They replay a forged payment-notification payload repeatedly, incrementing recorded payment amounts until target invoices are marked paid or overpaid. A detailed technical writeup and vendor advisory exist, but no packaged public exploit code was indicated in the input. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Unauthenticated attackers can bypass signature verification in FlexPrice's QuickBooks webhook handler (HandleQuickBooksWebhook) through version 2.1.38 by omitting the intuit-signature header, enabling forged payment notifications that can mark invoices paid or overpaid. Exploitation requires knowledge of a valid tenant and environment ID and an active, network-reachable QuickBooks integration; deployments not using QuickBooks webhooks are unaffected. No public exploit identified at time of analysis, though a public technical write-up is available, and this is a credible, moderate-to-high integrity risk.
RemediationAI
No vendor-released patch identified at time of analysis. Until a patched version is available, consider the following compensating controls: if the QuickBooks integration is not required, disable or block external access to the HandleQuickBooksWebhook endpoint (e.g., via firewall or reverse proxy rules). If the integration is needed, implement a WAF or reverse proxy rule to reject any request to the webhook endpoint that lacks the intuit-signature header, effectively enforcing the missing check at the edge; test carefully to avoid blocking legitimate QuickBooks webhooks. Additionally, restrict access to the endpoint to Intuit QuickBooks IP ranges, though this may break if QuickBooks changes its IPs and does not address the core flaw. Monitor logs for requests missing the intuit-signature header as a potential indicator of exploitation. For updates, monitor the VulnCheck advisory at https://www.vulncheck.com/advisories/flexprice-through-2.1.38-quickbooks-webhook-signature-verification-bypass and the FlexPrice GitHub repository at https://github.com/flexprice/flexprice.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a CWE-347 (Improper Verification of Cryptographic Signature) in FlexPrice's QuickBooks webhook integration. The HandleQuickBooksWebhook function in internal/api/v1/webhook.go (line 750) is designed to validate incoming payment notifications from Intuit QuickBooks using the intuit-signature header. However, when this header is omitted entirely, the code skips signature verification instead of rejecting the request, allowing an attacker to send arbitrary POST requests that are processed as legitimate. This bypass means no valid signature or shared secret is required; the attacker only needs to know a valid tenant ID and environment ID. The associated tags include Authentication Bypass and Jwt Attack, though the core defect is the missing signature check.
Know when Jwt Attack gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Network-reachable and unauthenticated (AV:N/PR:N), but needing valid tenant/environment IDs maps the 4.0 AT:P requirement to AC:H; impact is integrity-only (I:H, C:N/A:N).
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
DescriptionCVE.org
FlexPrice through 2.1.38 contains an authentication bypass vulnerability in HandleQuickBooksWebhook that skips signature verification when the intuit-signature header is omitted. Unauthenticated attackers knowing a tenant and environment ID can replay forged payment notifications to repeatedly add payment amounts, marking invoices paid or overpaid.
Executive ViewAI
FlexPrice deployments through version 2.1.38 that use QuickBooks webhooks are exposed to a high-severity integrity flaw that could let attackers forge payment notifications and falsely mark invoices as paid or overpaid. This creates financial reconciliation and fraud risk for finance and operations teams, but only where the QuickBooks integration is enabled and network-reachable. No vendor-released patch identified at time of analysis, so leadership should prioritize identifying affected instances and deciding whether to temporarily disable the integration.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling the QuickBooks webhook integration if not essential, restricting network reachability to the webhook endpoint via firewall or allowlist, enforcing rejection of requests missing the intuit-signature header at an upstream proxy or WAF where possible, rotating exposed tenant/environment identifiers, and monitoring or reconciling invoice payment statuses for unauthorized paid/overpaid changes.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Jwt Attack
View allWhy is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update
Authentication bypass in SimpleHelp 5.5.15 and prior (plus 6.0 pre-release builds) allows remote unauthenticated attacke
Authentication bypass in WSO2 API Manager and related components (Universal Gateway, Traffic Manager, API Control Plane,
Authentication bypass in Fortinet FortiOS, FortiProxy, and FortiSwitchManager allows unauthenticated remote attackers to
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT
Authentication and authorization bypass in fast-jwt 6.2.0 through 6.2.4 (npm, NearForm) lets a remote, unauthenticated a
A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti
A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27
A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work
The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t
EUVD-2026-101565
GHSA-mc76-h4x2-pgj7
NVD
CVE.org
EPSS
Exploit-DB