CVE-2023-7289

5.4 MEDIUM

📋 TL;DR

This vulnerability allows authenticated WordPress users with subscriber-level permissions to change the Paytium plugin's API keys without authorization. This affects WordPress sites using Paytium: Mollie payment forms & donations plugin versions up to 4.3.7. Attackers could redirect payments or disrupt payment processing functionality.

💻 Affected Systems

Products:
  • Paytium: Mollie payment forms & donations plugin for WordPress
Versions: Up to and including 4.3.7
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with Paytium plugin and at least one subscriber-level user account.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers redirect payment transactions to their own accounts, steal funds, and compromise payment data integrity.

🟠

Likely Case

Payment processing disruption, unauthorized transaction redirection, and potential financial loss.

🟢

If Mitigated

Limited impact with proper access controls, monitoring, and API key validation in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Requires authenticated access but only subscriber-level permissions. Simple HTTP request to vulnerable endpoint.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 4.3.8

Vendor Advisory: https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=2853869%40paytium%2Ftrunk&old=2824314%40paytium%2Ftrunk&sfp_email=&sfph_mail=#file0

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins. 3. Find Paytium plugin. 4. Click 'Update Now' or manually update to version 4.3.8+. 5. Verify update completes successfully.

🔧 Temporary Workarounds

Remove Subscriber Access

all

Temporarily disable or remove subscriber-level user accounts until patching.

wp user delete <username> --yes
wp user update <username> --role=no_role

Restrict API Endpoint

linux

Use web application firewall or .htaccess to block access to vulnerable endpoint.

# Add to .htaccess:
RewriteCond %{REQUEST_URI} ^/wp-admin/admin-ajax\.php$
RewriteCond %{QUERY_STRING} action=paytium_sw_save_api_keys
RewriteRule ^ - [F]

🧯 If You Can't Patch

  • Implement strict user role management and review all subscriber accounts
  • Enable detailed logging of API key changes and monitor for unauthorized modifications

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > Paytium plugin version. If version is 4.3.7 or lower, system is vulnerable.

Check Version:

wp plugin list --name=paytium --field=version

Verify Fix Applied:

Verify Paytium plugin version is 4.3.8 or higher in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized POST requests to /wp-admin/admin-ajax.php with action=paytium_sw_save_api_keys
  • Unexpected API key changes in plugin logs

Network Indicators:

  • HTTP POST requests to admin-ajax.php with API key parameters from non-admin users

SIEM Query:

source="wordpress.log" AND "paytium_sw_save_api_keys" AND user_role="subscriber"

🔗 References

📤 Share & Export