CVE-2025-67961

6.4 MEDIUM

📋 TL;DR

This Server-Side Request Forgery (SSRF) vulnerability in the WPO365 Login WordPress plugin allows attackers to make unauthorized requests from the vulnerable server to internal or external systems. It affects all WordPress sites using WPO365 Login plugin versions up to and including 40.0. Attackers could potentially access internal services or perform data exfiltration.

💻 Affected Systems

Products:
  • WPO365 Login WordPress Plugin
Versions: All versions up to and including 40.0
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Affects WordPress installations with the WPO365 Login plugin enabled.

⚠️ 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

Attackers could access internal services, exfiltrate sensitive data, or pivot to attack other internal systems from the compromised server.

🟠

Likely Case

Attackers could scan internal networks, access metadata services, or make requests to external systems while appearing to originate from the legitimate server.

🟢

If Mitigated

Limited impact if network segmentation restricts server outbound connections and internal services are properly firewalled.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

SSRF vulnerabilities typically have low exploitation complexity and may not require authentication depending on the specific implementation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Versions after 40.0

Vendor Advisory: https://patchstack.com/database/Wordpress/Plugin/wpo365-login/vulnerability/wordpress-wpo365-plugin-40-0-server-side-request-forgery-ssrf-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find WPO365 Login plugin. 4. Click 'Update Now' if available. 5. Alternatively, download latest version from WordPress repository and manually update.

🔧 Temporary Workarounds

Disable Plugin

all

Temporarily disable the vulnerable plugin until patched.

wp plugin deactivate wpo365-login

Network Restrictions

all

Restrict outbound HTTP/HTTPS requests from the web server to only necessary destinations.

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block SSRF patterns in requests
  • Deploy network segmentation to isolate the web server from sensitive internal services

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > Installed Plugins for WPO365 Login version. If version is 40.0 or lower, you are vulnerable.

Check Version:

wp plugin get wpo365-login --field=version

Verify Fix Applied:

After updating, verify the plugin version shows higher than 40.0 in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unusual outbound HTTP requests from web server to internal IPs or metadata services
  • Requests to unexpected domains from web server process

Network Indicators:

  • Web server making requests to internal IP ranges (10.x.x.x, 172.16.x.x, 192.168.x.x)
  • Requests to cloud metadata endpoints (169.254.169.254)

SIEM Query:

source="web_server_logs" AND (dest_ip=10.* OR dest_ip=172.16.* OR dest_ip=192.168.* OR dest_ip=169.254.169.254) AND http_method=GET

🔗 References

📤 Share & Export