CVE-2024-8269

7.3 HIGH

📋 TL;DR

The MStore API WordPress plugin allows unauthenticated attackers to create user accounts even when user registration is disabled. This affects all WordPress sites using MStore API plugin versions up to 4.15.3. Attackers can create administrative or regular user accounts to gain unauthorized access.

💻 Affected Systems

Products:
  • MStore API – Create Native Android & iOS Apps On The Cloud WordPress plugin
Versions: All versions up to and including 4.15.3
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerable regardless of whether user registration is enabled in WordPress settings or plugin functionality is activated.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers create administrative accounts, take over the WordPress site, install malware, deface content, or exfiltrate sensitive data.

🟠

Likely Case

Attackers create regular user accounts to spam, post malicious content, or use as foothold for further attacks.

🟢

If Mitigated

With proper monitoring and user role restrictions, impact is limited to cleanup of unauthorized accounts.

🌐 Internet-Facing: HIGH
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Simple HTTP POST request to vulnerable endpoint with user registration parameters.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 4.15.4

Vendor Advisory: https://plugins.trac.wordpress.org/changeset/3147900/mstore-api/trunk/controllers/flutter-user.php

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find MStore API plugin. 4. Click 'Update Now' if update available. 5. If no update appears, manually download version 4.15.4+ from WordPress.org and replace plugin files.

🔧 Temporary Workarounds

Disable MStore API plugin

all

Temporarily deactivate the vulnerable plugin until patched.

wp plugin deactivate mstore-api

Block vulnerable API endpoint

linux

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

RewriteEngine On
RewriteRule ^wp-json/flutter-user/register - [F,L]

🧯 If You Can't Patch

  • Implement rate limiting on /wp-json/flutter-user/register endpoint
  • Enable detailed logging of user registration attempts and monitor for suspicious activity

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → MStore API version. If version is 4.15.3 or lower, you are vulnerable.

Check Version:

wp plugin get mstore-api --field=version

Verify Fix Applied:

After updating, verify plugin version shows 4.15.4 or higher in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Multiple POST requests to /wp-json/flutter-user/register endpoint
  • Unusual user account creations with similar usernames/emails

Network Indicators:

  • HTTP POST requests to /wp-json/flutter-user/register from unexpected IPs
  • Burst of registration attempts

SIEM Query:

source="web_logs" AND uri_path="/wp-json/flutter-user/register" AND http_method="POST" | stats count by src_ip

🔗 References

📤 Share & Export