Description
The iPOSpays Payment Gateway for WooCommerce WordPress plugin before 1.4.7 does not verify that a payment was actually completed before recording an order as paid, allowing unauthenticated users to mark any unpaid order as paid and to rewrite its total.
Published: 2026-10-19
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized Payment Confirmation Forgery
Action: Patch
AI Analysis

Impact

The iPOSpays Payment Gateway for WooCommerce plugin does not confirm that a payment has actually been completed before marking an order as paid. As a result, an unauthenticated user can send a request that changes an unpaid order to paid and modifies the order total. This allows creation of false payment records and can enable fraudulent payouts or revenue loss for the merchant ownership or the customer business.

Affected Systems

All installations of the iPOSpays Payment Gateway for WooCommerce WordPress plugin with a version lower than 1.4.7 are affected. The product is developed and distributed under the iPOSpays branding, and no other vendors or product variants are listed.

Risk and Exploitability

The CVSS score of 5.3 indicates a moderate severity that may compromise system integrity. EPSS is not available, so the likelihood of automated exploitation is uncertain, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is an unauthenticated HTTP request to the plugin’s payment confirmation endpoint or a related REST API call that does not enforce proper access control. Because the flaw stems from inadequate authentication checks before status changes (CWE-345), an attacker can forge payment confirmations without needing credentials, thereby achieving privilege escalation within the order processing workflow.

Generated by OpenCVE AI on October 19, 2026 at 11:45 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the iPOSpays Payment Gateway for WooCommerce to version 1.4.7 or later, which validates payment completion before marking orders as paid.
  • If an update cannot be performed immediately, restrict the plugin’s payment‑handling endpoints so that only authenticated administrators or the payment gateway webhook can invoke them—this can be enforced via a web application firewall or by tightening user role permissions.
  • Ensure that every order status transition is logged and cross‑checked against the actual payment gateway response before finalizing the status change.

Generated by OpenCVE AI on October 19, 2026 at 11:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 19 Oct 2026 10:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-345
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 19 Oct 2026 07:00:00 +0000

Type Values Removed Values Added
Description The iPOSpays Payment Gateway for WooCommerce WordPress plugin before 1.4.7 does not verify that a payment was actually completed before recording an order as paid, allowing unauthenticated users to mark any unpaid order as paid and to rewrite its total.
Title iPOSpays Payment Gateway for WooCommerce < 1.4.7 - Unauthenticated Payment Confirmation Forgery
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-10-19T09:31:21.374Z

Reserved: 2026-09-08T11:53:30.380Z

Link: CVE-2026-86791

cve-icon Vulnrichment

Updated: 2026-10-19T09:25:22.006Z

cve-icon NVD

Status : Received

Published: 2026-10-19T07:16:32.043

Modified: 2026-10-19T10:16:49.650

Link: CVE-2026-86791

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-19T12:00:16Z

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity