Skip to main content

Snap Finance EUVDEUVD-2026-104106

| CVE-2026-94272 MEDIUM
Missing Authorization (CWE-862)
2026-10-19 WPScan GHSA-9j58-p96w-684h
5.3
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 Snap Finance plugin <3.12.0
  2. Delivery
    Send crafted unauthenticated status-change request
  3. Exploit
    Bypass missing authorisation check
  4. Execution
    Force target order to paid or failed state
  5. Impact
    Obtain goods or disrupt merchant fulfilment

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
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

Requires only that the Snap Finance WordPress plugin before version 3.12.0 be installed and active on a WooCommerce store; the vulnerable order-status-change request handler performs no verification that the request comes from an authorised source, so no authentication, no user interaction, and no non-default configuration are needed (AV:N/AC:L/PR:N/UI:N). The practical limiting factors are narrow: the site must run this specific plugin and WooCommerce, and impact is bounded to altering order status (e.g., forcing 'paid' or 'failed') - there is no data read or site takeover, so realistic harm is payment/fulfilment fraud and transaction disruption rather than full compromise.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, base 5.3 Medium) describes a cleanly remote, unauthenticated, low-complexity broken-access-control flaw with no user interaction, but limited to a low integrity impact and zero confidentiality or availability impact - consistent with the description, which permits manipulating WooCommerce order state (paid/failed) rather than reading data or taking over the site. Publicly available exploit code (reported by WPScan) raises practical risk, but there is no CISA KEV listing and no EPSS score was provided, so there is no evidence of active exploitation - this is best treated as POC-available, not in-the-wild. The signals are internally consistent (unauthenticated network vector matches the 'authorised source not verified' description); the main caveat is that CVSS caps this at Medium because only order status integrity is affected, yet the real-world business impact (fraudulently forcing orders into a 'paid' state to obtain goods without payment) may exceed what a 5.3 implies for a merchant. Net: a genuine, easily-exploitable access-control bug worth prompt patching for affected stores, but lower blast radius than a code-execution or data-exposure flaw and not a mass-exploitation emergency.

Exploit ScenarioDerived

An attacker sends a crafted, unauthenticated HTTP request to the vulnerable Snap Finance plugin endpoint that changes a WooCommerce order's status, without any valid authorisation token. Because the plugin does not verify the request source, the attacker forces a target order into a 'paid' state (potentially triggering fulfilment of goods without real payment) or into a 'failed' state to disrupt legitimate transactions. Public exploit code exists (WPScan), lowering the skill required to reproduce the attack.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 19, 2026

Unauthenticated WooCommerce order-status manipulation in the Snap Finance WordPress plugin before 3.12.0 allows remote attackers to mark arbitrary orders as paid or failed because the status-change handler does not verify that the request comes from an authorised source. The flaw has a CVSS 3.1 base score of 5.3 Medium (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N), with impact limited to order-state integrity and no confidentiality or availability impact. Publicly available exploit code exists, but no CISA KEV entry was provided indicating confirmed active exploitation.

RemediationAI

Upgrade the Snap Finance WordPress plugin to version 3.12.0 or later, which is the vendor-advertised fixed release, and confirm the update through the WordPress admin plugin page; the WPScan advisory at https://wpscan.com/vulnerability/e3a4931a-3678-46ac-9ad0-3cc6a1ed5d90/ should be reviewed for any additional vendor guidance. If upgrading immediately is not possible, deactivate the Snap Finance plugin until patched, accepting that this removes Snap Finance checkout/financing functionality from the WooCommerce store. As a compensating control, restrict or block unauthenticated access to the plugin's order-status-changing AJAX/REST endpoints using a web application firewall or reverse-proxy rule, but test this carefully because legitimate checkout callbacks and storefront flows may depend on those routes. Store owners should also review recent WooCommerce orders for unexpected paid or failed status changes and reconcile them against payment provider records.

Affected VersionsENISA

Snap Finance 1.0.8 <3.12.0

Affected Packages

euvd snap_finance fix: 3.12.0

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 issue is in a WordPress plugin that integrates Snap Finance financing with WooCommerce order processing. WooCommerce order status values such as paid and failed drive payment reconciliation, fulfilment, and customer communication, so a handler that changes status without validating the request source creates a broken-access-control condition. The provided CPE cpe:2.3:a:unknown:snap_finance:*:*:*:*:*:*:*:* identifies the Snap Finance plugin, with the vendor field not resolved, and the advisory indicates all versions before 3.12.0 are affected. No CWE was supplied, but the root-cause class is missing authorization/source verification on a state-changing request. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, exploitation is remote, low-complexity, unauthenticated, and requires no user interaction, but the assessed impact is only low integrity loss rather than data disclosure or site takeover.

Know when Snap Finance 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 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
vuln.today AI 5.3 MEDIUM

Unauthenticated remote request with no interaction (AV:N/AC:L/PR:N/UI:N); only order-status integrity is affected (I:L), with no confidentiality or availability impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/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
None
Integrity
Low
Availability
None

Lifecycle Timeline

2
Patch available
Oct 19, 2026 - 08:01 EUVD
CVE Published
Oct 19, 2026 - 06:46 cve.org
MEDIUM 5.3

DescriptionCVE.org

The Snap Finance WordPress plugin before 3.12.0 does not verify that a request to change a WooCommerce order's status comes from an authorised source, allowing unauthenticated attackers to move any order into a paid state or force it to fail.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Low
niche BNPL payment plugin for WooCommerce, limited merchant footprint
Exploit
POC
Public exploit code exists
Social Media
2
Sightings
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 MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
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· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

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

Attack Technique

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