Skip to content
Noroxi

Mollie Payments for WooCommerce

mollie-payments-for-woocommerce · plugin

Known security vulnerabilities for Mollie Payments for WooCommerce. Find out in seconds which version runs on your site with WP Lens.

6 known vulnerabilities

5 exploitable without logging in · latest Nov 4, 2026

Before you install

Use with care

  • 4 records needing no login published in the last two years.

If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.

This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.

Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector

Listed on wordpress.org · latest 8.1.11 · last updated Oct 12, 2026 · 100K+ installs

wordpress.org status checked on Oct 26, 2026

Vulnerabilities

  • CVE-2023-6090high privilege≤ 7.3.11

    WordPress Mollie Payments for WooCommerce Plugin <= 7.3.11 is vulnerable to Arbitrary File Upload

    High 7.2

  • CVE-2025-68501unauthenticated · needs a click≤ 8.1.1

    WordPress Mollie Payments for WooCommerce plugin <= 8.1.1 - Reflected Cross Site Scripting (XSS) vulnerability

    High 7.1

  • CVE-2025-39362unauthenticated≤ 8.0.2

    WordPress Mollie Payments for WooCommerce plugin <= 8.0.2 - Insecure Direct Object References (IDOR) vulnerability

    Medium 6.5

  • CVE-2024-6448unauthenticated≤ 7.7.0

    Mollie Payments for WooCommerce <= 7.7.0 - Unauthenticated Full Path Disclosure

    Medium 5.3

  • CVE-2026-101166unauthenticated→ 8.2.0

    Mollie Payments for WooCommerce < 8.2.0 - Unauthenticated Unpublished Product Purchase via mollie_paypal_create_order

    Low 3.7

  • CVE-2026-101165unauthenticated→ 8.2.0

    Mollie Payments for WooCommerce < 8.2.0 - Unauthenticated Payment Surcharge Bypass via update_surcharge_order_pay

    Low 3.7

The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).

← Back to directory