Description
The Visma Pay for WooCommerce WordPress plugin before 1.2.2 does not verify the authenticity of payment gateway return requests, relying on a merchant secret that is empty on a store which has not entered its credentials, allowing unauthenticated attackers to mark arbitrary orders as paid and to disclose the name, email address and postal address of any order's customer.
Published: 2026-10-14
Score: 6.5 Medium
EPSS: n/a
KEV: No
Impact: Unauthorized Payment Bypass and Customer Data Disclosure
Action: Immediate Patch
AI Analysis

Impact

Visma Pay for WooCommerce before 1.2.2 does not authenticate gateway return requests, using an empty merchant secret when credentials are missing. This flaw lets an unauthenticated attacker trigger the payment confirmation endpoint, marking arbitrary orders as paid and enabling the attacker to retrieve the name, email address and postal address of any customer who placed an order. The impact is unauthorized financial processing and exposure of personally identifiable information, compromising order integrity and customer confidentiality.

Affected Systems

The vulnerability affects the Visma Pay for WooCommerce WordPress plugin on any store running a version earlier than 1.2.2. The plugin is available through the WordPress plugin repository and is used in WordPress sites that have not configured a merchant secret.

Risk and Exploitability

The CVSS score of 6.5 indicates a moderate severity. EPSS data is not available, so the likelihood of exploitation cannot be quantified from the current data, but the lack of authentication on a publicly exposed payment endpoint makes exploitation straightforward for attackers with no credentials. The vulnerability is not listed in the CISA KEV catalog, however the attack vector is external and unauthenticated, and the impact includes potential financial fraud and data leakage.

Generated by OpenCVE AI on October 14, 2026 at 13:59 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Visma Pay for WooCommerce to version 1.2.2 or later, which validates the authenticity of gateway return requests and requires a merchant secret.
  • Configure the plugin with a non‑empty merchant secret to prevent the return endpoint from accepting requests unconditionally.
  • If an upgrade is not immediately possible, restrict access to the gateway return endpoint to traffic from the payment gateway’s IP addresses or add additional authentication checks to the endpoint.

Generated by OpenCVE AI on October 14, 2026 at 13:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 14 Oct 2026 14: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'}


Wed, 14 Oct 2026 14:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-20
CWE-200
CWE-285

Wed, 14 Oct 2026 10:45:00 +0000

Type Values Removed Values Added
Description The Visma Pay for WooCommerce WordPress plugin before 1.2.2 does not verify the authenticity of payment gateway return requests, relying on a merchant secret that is empty on a store which has not entered its credentials, allowing unauthenticated attackers to mark arbitrary orders as paid and to disclose the name, email address and postal address of any order's customer.
Title Visma Pay for WooCommerce < 1.2.2 - Unauthenticated Payment Bypass and Order Data Disclosure via Gateway Return Endpoint
References
Metrics cvssV3_1

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


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-10-14T13:33:35.512Z

Reserved: 2026-09-30T11:35:56.857Z

Link: CVE-2026-103308

cve-icon Vulnrichment

Updated: 2026-10-14T10:43:50.453Z

cve-icon NVD

Status : Deferred

Published: 2026-10-14T11:16:57.547

Modified: 2026-10-14T16:14:02.800

Link: CVE-2026-103308

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-14T14:00:17Z

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-285

    Improper Authorization

  • CWE-345

    Insufficient Verification of Data Authenticity