dbcve.org
Mollie Payments For WoocommerceWordPress extension · Mollie

CVE-2023-6090

HIGH · 7.2 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to 7.3.12 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unrestricted Upload of File with Dangerous Type vulnerability in Mollie Mollie Payments for WooCommerce.This issue affects Mollie Payments for WooCommerce: from n/a through 7.3.11.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an unrestricted file upload vulnerability in the Mollie Payments for WooCommerce plugin (versions through 7.3.11). The flaw allows attackers to upload dangerous file types (potentially executable scripts like PHP files) to the server without proper validation or restrictions, which could lead to remote code execution if the uploaded files are accessible and executed.

MitigationApply the vendor patch/upgrade to version 7.3.12 or later, which adds proper file type validation, restricts upload locations, and prevents execution of uploaded files. Until patched, disable the plugin or restrict admin access to minimize exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mollie Payments For WoocommerceWordPress extension
Affected:< 7.3.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Mollie Payments for WooCommerce is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Mollie Payments for WooCommerce' by Mollie. Alternatively, check the plugin directory /wp-content/plugins/mollie-payments-for-woocommerce/ for the main plugin file and review its version header.
    Affected if The plugin is installed and active on the WordPress site.
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on the plugin name to view the version, or open the main plugin PHP file (usually mollie-payments-for-woocommerce.php) and read the Version header in the plugin comment block.
    Affected if The version number is less than 7.3.12 (e.g., 7.3.11, 7.3.10, etc.).
  3. Verify the upload functionality is accessible
    Navigate to WooCommerce > Settings > Payments > Mollie Payments. Check if the plugin settings allow or configure payment method setup that includes any file upload or logo upload features accessible to users or administrators.
    Affected if The plugin configuration allows file uploads (such as uploading payment logos or other attachments) and the uploads directory is web-accessible.
  4. Inspect the uploads directory accessibility
    Check the /wp-content/uploads/ directory via the file system or a web request to see if uploaded files are served directly by the web server (bypassing PHP execution restrictions). Attempt to access a known uploaded file type directly via browser.
    Affected if The uploads directory allows direct file access without execution restrictions (e.g., .php files can be accessed and executed by the web server).

A site is affected if it has Mollie Payments for WooCommerce version below 7.3.12 installed and the plugin or its settings allow file uploads to a web-accessible directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.3.12 or later
Fixed in 7.3.12
Interim mitigation

Apply the vendor patch/upgrade to version 7.3.12 or later, which adds proper file type validation, restricts upload locations, and prevents execution of uploaded files. Until patched, disable the plugin or restrict admin access to minimize exposure.

Recommended fix High confidence

7.3.12

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Mollie Payments for WooCommerce' in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 7.3.12 from the WordPress plugin repository
  5. Verify the update completed successfully
  6. Test that payment processing still works correctly
  7. Clear any caching if applicable

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mollie Payments For Woocommerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6090 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6090 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data