CVE-2025-7444

9.8 CRITICAL

📋 TL;DR

The LoginPress Pro WordPress plugin has an authentication bypass vulnerability that allows unauthenticated attackers to log in as any existing user, including administrators, if they know the user's email address and the user doesn't have an existing account with the social login service. This affects all WordPress sites using LoginPress Pro up to version 5.0.1. Attackers can gain full administrative access to vulnerable WordPress installations.

💻 Affected Systems

Products:
  • LoginPress Pro WordPress Plugin
Versions: All versions up to and including 5.0.1
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires social login feature to be enabled and configured. Vulnerability exists in the social login token verification mechanism.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete site takeover - attackers gain administrator access, can install backdoors, deface websites, steal sensitive data, and compromise the entire WordPress installation and potentially the underlying server.

🟠

Likely Case

Administrative account compromise leading to content manipulation, plugin/theme installation, user creation, and data exfiltration.

🟢

If Mitigated

Limited impact if social login is disabled or if all users already have accounts with social login services, though the vulnerability still exists in the codebase.

🌐 Internet-Facing: HIGH - WordPress sites are typically internet-facing, and the vulnerability requires no authentication, making all vulnerable sites immediately exploitable from anywhere.
🏢 Internal Only: MEDIUM - Internal WordPress sites are still vulnerable if accessible to internal attackers, but exposure is limited to the internal network.

🎯 Exploit Status

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

The vulnerability is straightforward to exploit once the attack vector is understood. Attackers need target user email addresses and knowledge that those users don't have existing social login accounts.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Version 5.0.2 or later

Vendor Advisory: https://loginpress.pro/changelog/

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find LoginPress Pro and check if update is available. 4. Click 'Update Now' to update to version 5.0.2 or later. 5. Verify the update completed successfully.

🔧 Temporary Workarounds

Disable Social Login Feature

all

Temporarily disable the social login functionality in LoginPress Pro settings until patching is possible.

Disable LoginPress Pro Plugin

linux

Deactivate the LoginPress Pro plugin completely if social login is not essential for your site.

wp plugin deactivate loginpress-pro

🧯 If You Can't Patch

  • Implement Web Application Firewall (WAF) rules to block suspicious authentication attempts
  • Enable two-factor authentication for all administrative accounts

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → Installed Plugins → LoginPress Pro version. If version is 5.0.1 or lower, the site is vulnerable.

Check Version:

wp plugin get loginpress-pro --field=version

Verify Fix Applied:

After updating, verify LoginPress Pro version is 5.0.2 or higher in WordPress plugins list.

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed login attempts followed by successful login from new IP addresses
  • Successful logins via social login for users who previously didn't use social login
  • Administrative actions from unexpected IP addresses or user accounts

Network Indicators:

  • Unusual authentication patterns to /wp-admin/admin-ajax.php or social login endpoints
  • Traffic spikes to social login callback URLs

SIEM Query:

source="wordpress.log" AND ("social-login" OR "oauth" OR "loginpress") AND status="200" AND user_agent NOT IN ["normal_user_agents"]

🔗 References

📤 Share & Export