Skip to main content

Fundiin WooCommerce CVE-2026-81649

| EUVDEUVD-2026-96752 CRITICAL
Incorrect Authorization (CWE-863)
2026-10-11 WPScan GHSA-v54w-6hqg-rx6f
9.1
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify store running Fundiin plugin
  2. Delivery
    Send REST request with shared hardcoded credential
  3. Exploit
    Bypass authorization on unprotected routes
  4. Execution
    Exfiltrate payment credentials and overwrite gateway config
  5. Impact
    Redirect payments and mark orders paid

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The core flaw requires no special conditions: several REST API routes enforce authorization only via a credential that is hardcoded identically across every installation, so remote unauthenticated attackers can invoke the credential-disclosure, order-data, gateway-reconfiguration, and mark-as-paid functions against default installs of the Fundiin cho WooCommerce plugin (version ≤3.4.0). The one explicitly limiting factor is for the stored-XSS component: it only affects stores using the classic WooCommerce checkout, because the injected script is output unescaped there - stores configured with the block-based checkout are not vulnerable to the XSS (though they remain exposed to the authorization-bypass data/financial impacts). Overall exposure is further bounded by whether the Fundiin plugin is installed and active at all.

Impact

All signals point to a genuine high-priority issue rather than a CVSS-inflated one. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N, C:H/I:H) is fully consistent with the description: the plugin relies on a credential that is identical on every installation, which is functionally equivalent to no authorization (CWE-863), so any remote, unauthenticated attacker can reach the vulnerable REST routes with low complexity. Publicly available exploit code exists (reported by WPScan), which materially raises real-world risk, though this is distinct from confirmed active exploitation - the CVE is NOT in CISA KEV, and no EPSS score was supplied, so widespread automated exploitation cannot be confirmed from the data. No SSVC decision data was provided. The impact is severe and multi-faceted (payment-credential and customer-order disclosure, payment-gateway reconfiguration to redirect funds, fraudulent marking of orders as paid, and unauthenticated stored XSS on classic checkout), making it attractive for financially motivated attackers. The main factor limiting blast radius is deployment footprint: this is a niche BNPL payment plugin, not ubiquitous software, so exploitation is likely to be opportunistic/targeted against stores that run it rather than internet-wide.

Exploit ScenarioDerived

An unauthenticated attacker locates a WooCommerce store running the Fundiin plugin and sends crafted HTTP requests to its unprotected REST API routes using the shared, install-independent credential. They dump the store's payment credentials and customer order data, rewrite the payment-gateway configuration so future payments are credited to an attacker-controlled account, and mark unpaid orders as paid; a public exploit (WPScan) exists. On stores using the classic (non-block) checkout, they can also store arbitrary script in an unescaped field, yielding stored XSS against checkout visitors.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 11, 2026

Unauthenticated remote attackers can seize control of the payment configuration on WordPress stores running the Fundiin cho WooCommerce plugin through 3.4.0, because several of its REST API routes enforce authorization only through a credential that is hardcoded identically in every installation. Exploiting this yields disclosure of the store's payment gateway credentials and customer order data, allows the gateway configuration to be rewritten so that payments are credited to an attacker-controlled destination, and permits unpaid orders to be marked as paid; the same missing authorization additionally allows script to be stored and rendered unescaped on the classic WooCommerce checkout, producing unauthenticated stored XSS. CVSS 3.1 scores this 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) and publicly available exploit code exists per the WPScan report, while no CISA KEV entry was present in the supplied intelligence.

RemediationAI

No vendor-released patch version is identified in the available intelligence, so remediation should begin with removing the exposure: if Fundiin payments are not in active use, deactivate and delete the plugin outright, which eliminates both the authorization bypass and the stored-XSS sink. If the plugin must stay online, restrict access to its REST namespace at the reverse proxy or WAF so that only the store's own servers and Fundiin callbacks can reach those routes, accepting the trade-off that over-blocking can break checkout callbacks and payment status updates. Because the shared credential is identical on every installation, treat it as public: rotate the Fundiin merchant/gateway credentials and any other secrets the plugin stores, and treat previously stored payment credentials as compromised. Audit orders created or modified during the plugin's deployment window for fraudulent "paid" markings and reconcile settlements against the gateway, since altered gateway configuration can silently redirect funds; reverting the gateway settings from a known-good backup is advised. Migrating the store to the block-based WooCommerce checkout removes the unescaped-output XSS vector but provides no protection against the underlying authorization bypass. Until a fixed release is confirmed and deployed, monitor the plugin's REST routes for unexpected callers and watch for injected script on the classic checkout pages. Patch status per available data: no vendor-released patch identified at time of analysis.

Affected VersionsENISA

Fundiin cho WooCommerce 0 ≤3.4.0

Affected Packages

euvd fundiin_cho_woocommerce no fix

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 root cause is CWE-863 (Incorrect Authorization). WordPress plugins expose functionality through the REST API by registering routes with register_rest_route(), where a permission_callback is supposed to gate access. In Fundiin cho WooCommerce through 3.4.0, several routes instead validate a static credential that is baked into the plugin and therefore identical across all deployments; a value that ships in every copy of the code provides no real authentication boundary, so any remote party able to reach the site's REST endpoint can invoke privileged operations without a WordPress account. That single weakness fans out into four impacts: reading stored payment gateway credentials, reading customer order data, overwriting the payment gateway configuration (redirecting settlement of payments), and flipping unpaid orders to a paid state. Separately, one of the fields handled by these routes is persisted without sanitization and later output without escaping in the classic (shortcode/template-based) WooCommerce checkout, converting the authorization bypass into unauthenticated stored XSS against shoppers; stores built on the block-based checkout render that data through the block layer and are not exposed to the XSS component, though they remain fully exposed to the authorization-bypass data and financial impacts. The CPE supplied by the feed (cpe:2.3:a:unknown:fundiin_cho_woocommerce:*:*:*:*:*:*:*:*) leaves the vendor namespace unassigned, so version confirmation relies on the EUVD range (Fundiin cho WooCommerce 0 through 3.4.0) rather than CPE matching.

Know when Fundiin Cho Woocommerce 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

Vendor (WPScan) PRIMARY 9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 9.1 CRITICAL

A shared install-wide credential is effectively no authorization, so PR:N/AC:L over the network; high confidentiality (credential/order disclosure) and integrity (config overwrite, mark-paid) impact, with no availability effect.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

3
CVSS changed
Oct 11, 2026 - 12:22 NVD
9.1 (CRITICAL)
CVE Published
Oct 11, 2026 - 06:00 cve.org
CRITICAL 9.1
CVE Published
Oct 11, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The Fundiin cho WooCommerce WordPress plugin through 3.4.0 does not have proper authorisation on several of its REST API routes, relying instead on a credential that is identical on every installation, allowing unauthenticated attackers to disclose the store's payment credentials and customer order data, overwrite the payment gateway configuration so that payments are credited elsewhere, and mark unpaid orders as paid. The same missing authorisation also allows arbitrary script to be stored in a field which is output unescaped on the classic checkout, leading to unauthenticated stored XSS on stores that do not use the block-based checkout.

Technical POC Analysis

Bug class: CWE-863 Incorrect Authorization.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

The Fundiin cho WooCommerce payment plugin (through version 3.4.0) lets an unauthenticated attacker take over the payment configuration of any WordPress store running it, allowing payments to be silently redirected to an attacker-controlled account while unpaid orders are marked as paid. Because every installation ships with the same hardcoded authorization credential, any store using this plugin is exposed, and compromise also leaks payment gateway credentials and customer order data and plants persistent malicious script on the checkout page. Leadership should treat this as a direct financial and customer-data risk affecting revenue integrity, payment-processor relationships, and PCI obligations, with remediation complicated by the absence of a vendor patch.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the Fundiin cho WooCommerce plugin (through 3.4.0) if it is not business-critical; block the plugin's REST API routes and restrict /wp-json at the WAF, reverse proxy, or web server; rotate all payment gateway credentials, API keys, and webhook secrets; enforce least-privilege and MFA on WordPress administrative accounts; monitor and reconcile order status changes and gateway payout destinations; and treat all transactions processed since exposure as potentially tampered.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Low
niche Vietnamese BNPL payment plugin for WooCommerce, limited store adoption
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
CRITICAL severity + public POC available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

66
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy