CVE-2025-68564

6.5 MEDIUM

📋 TL;DR

This CVE describes a missing authorization vulnerability in the Sendy WordPress plugin that allows attackers to bypass access controls. It affects Sendy plugin installations from all versions up to and including 3.4.2. WordPress sites using vulnerable versions of the Sendy plugin are at risk of unauthorized access to restricted functionality.

💻 Affected Systems

Products:
  • Sendy WordPress Plugin
Versions: n/a through <= 3.4.2
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all WordPress installations using vulnerable Sendy plugin versions regardless of configuration.

⚠️ 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 compromise of the WordPress site through privilege escalation, allowing attackers to modify content, install malicious plugins, or take full administrative control.

🟠

Likely Case

Unauthorized access to sensitive plugin functionality, potentially allowing attackers to manipulate email lists, access subscriber data, or modify plugin settings.

🟢

If Mitigated

Limited impact with proper network segmentation and additional authentication layers, though the vulnerability still exists in the codebase.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires some understanding of WordPress plugin structure but is technically straightforward once the vulnerability is understood.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: > 3.4.2

Vendor Advisory: https://patchstack.com/database/Wordpress/Plugin/sendy/vulnerability/wordpress-sendy-plugin-3-2-7-broken-access-control-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find Sendy plugin. 4. Click 'Update Now' if update available. 5. If no update available, deactivate and remove plugin, then install latest version from WordPress repository.

🔧 Temporary Workarounds

Temporary Plugin Deactivation

all

Disable the Sendy plugin until patched version is available

wp plugin deactivate sendy

Access Restriction via .htaccess

linux

Restrict access to Sendy plugin directories

# Add to .htaccess in wp-content/plugins/sendy/
Order Deny,Allow
Deny from all

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block suspicious access patterns to Sendy endpoints
  • Enable detailed logging and monitoring for unauthorized access attempts to Sendy plugin functionality

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel → Plugins → Installed Plugins for Sendy version. If version is 3.4.2 or lower, system is vulnerable.

Check Version:

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

Verify Fix Applied:

Verify Sendy plugin version is greater than 3.4.2 in WordPress admin panel and test access controls for restricted functionality.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to Sendy plugin endpoints
  • Multiple failed authentication attempts followed by successful access to restricted Sendy functions

Network Indicators:

  • Unusual HTTP requests to /wp-content/plugins/sendy/ paths from unauthorized IPs
  • POST requests to Sendy admin endpoints without proper authentication headers

SIEM Query:

source="wordpress.log" AND (uri_path="/wp-content/plugins/sendy/*" AND (response_code=200 OR response_code=302) AND NOT user_agent="WordPress/*")

🔗 References

📤 Share & Export