medium · CVSS v3 5.3 · EPSS 0.00136

CVE-2026-94273

The Snap Finance WordPress plugin up to version 3.11.0 fails to verify the payment provider’s response before marking a WooCommerce order as

Overview

The Snap Finance WordPress plugin up to version 3.11.0 fails to verify the payment provider’s response before marking a WooCommerce order as paid. This flaw allows unauthenticated attackers to mark arbitrary orders as paid without completing payment, potentially leading to revenue loss and inventory mismanagement. The issue is a medium‑severity vulnerability that can affect any site using the affected plugin.

Description

The Snap Finance WordPress plugin through 3.11.0 does not verify that the payment provider's response actually confirms a completed, approved transaction before marking a WooCommerce order as paid, allowing unauthenticated attackers to mark arbitrary orders as paid without completing payment.

Impact

Confidentiality: attackers may gain insight into order details. Integrity: unauthorized orders can be marked as paid, corrupting order records. Availability: not directly impacted. Defenders include site owners, e-commerce managers, and payment processors who must ensure accurate payment confirmation.

Remediation

1. Update the Snap Finance plugin to the latest version (≥3.11.1). 2. Verify the payment provider’s response code and status before changing the order status to paid. 3. If an update is not possible, disable automatic status changes and manually confirm payments. 4. Monitor order logs for unexpected status changes and audit payment processing workflows.

Risk context

The vulnerability has a medium CVSS v3 score of 5.3 and an EPSS of 0.00136, indicating a low probability of exploitation but still requiring timely patching to mitigate potential financial impact.

Affected products

  • Snap Finance WordPress plugin
  • WooCommerce

Scores

Severity
medium
CVSS v2
5
CVSS v3
5.3
CVSS v4
—
EPSS
0.00136

WordPress WooCommerce Payment Order Authentication Integrity E-commerce

← All CVEs

Related CVEs

medium

CVE-2026-112091

A flaw has been found in Dav-ee dairy-management-system 31ace9692d1e1e6d64339a42c463b361319c615c/f31a584c3330c013b61f8b0306d9e0849c6d693d. Impacted is an unknown function of the file delivery/checkfarmer.json.php of the component AJAX Endpoint. This manipulation of the argument fname causes information disclosure. Remote exploitation of the attack is possible. The exploit has been published and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The project was informed of the problem early through an issue report but has not responded yet.

View analysis

medium

CVE-2026-112092

A flaw has been found in subhajitkhan online-clinic-management-system up to e9ee77a8827a1446220fa07ee693dc4d9a29a578. The affected element is the function echo of the file doctorregistration.php of the component Doctor Registration. Executing a manipulation of the argument doc_name can lead to cross site scripting. It is possible to launch the attack remotely. The exploit has been published and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The project was informed of the problem early through an issue report but has not responded yet.

View analysis

medium

CVE-2026-112095

A flaw has been found in SourceCodester Inventory System 1.0. This affects an unknown part of the file /api/products_handler.php?action=save of the component Product Management. Executing a manipulation of the argument Product_Id/Product_Name can lead to cross site scripting. The attack may be performed from remote. The exploit has been published and may be used.

View analysis

medium

CVE-2026-85249

Improper Input Validation vulnerability in Apache Camel Tika component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. The Tika producer mapped every metadata key parsed out of the submitted document onto the Exchange as a header, with no filter applied. Document metadata is attacker-controlled content: the party that supplies the file chooses the metadata keys it carries. A crafted document could therefore set Exchange headers that the rest of the route depends on, including headers in the Camel namespace such as CamelFileName, which downstream components use to decide where content is written. The pattern is the same header-injection class as the consumer advisories published previously, reached here through parsed file content rather than through a protocol header. Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. Parsed document metadata is now filtered through a HeaderFilterStrategy before it is mapped onto the Exchange. A route that was reading a metadata-derived header the filter now blocks will see it missing. For deployments that cannot upgrade immediately, strip the Camel namespace after the Tika producer with removeHeaders("Camel*") before any component that acts on those headers.

View analysis