CVE-2026-24536

7.5 HIGH

📋 TL;DR

The Webpushr WordPress plugin (versions up to and including 4.38.0) contains a vulnerability that allows unauthorized users to retrieve sensitive system information embedded in the plugin. This affects all WordPress sites running the vulnerable plugin version, potentially exposing configuration details or other sensitive data.

💻 Affected Systems

Products:
  • Webpushr Web Push Notifications WordPress Plugin
Versions: n/a through <= 4.38.0
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all WordPress installations with the vulnerable plugin version installed and activated.

⚠️ 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 obtain sensitive system information, API keys, or configuration details that could lead to further attacks like privilege escalation or complete site compromise.

🟠

Likely Case

Unauthorized users accessing sensitive system information that could be used for reconnaissance or to facilitate other attacks.

🟢

If Mitigated

Limited exposure of non-critical system information with proper access controls and monitoring in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Based on CWE-497 description, this appears to be an information disclosure vulnerability that likely requires minimal technical skill to exploit.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: > 4.38.0

Vendor Advisory: https://patchstack.com/database/Wordpress/Plugin/webpushr-web-push-notifications/vulnerability/wordpress-webpushr-plugin-4-38-0-sensitive-data-exposure-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel
2. Navigate to Plugins → Installed Plugins
3. Find Webpushr Web Push Notifications
4. Click 'Update Now' if available
5. Alternatively, download latest version from WordPress repository
6. Deactivate and delete old version, then install fresh copy

🔧 Temporary Workarounds

Disable Plugin

all

Temporarily deactivate the Webpushr plugin until patched

wp plugin deactivate webpushr-web-push-notifications

Access Restriction

linux

Restrict access to WordPress admin and plugin endpoints

# Add to .htaccess for Apache:
<FilesMatch "\.(php|inc)$">
Order Deny,Allow
Deny from all
</FilesMatch>
# Add to nginx config:
location ~ /\.php$ {
    deny all;
}

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block suspicious requests to plugin endpoints
  • Enable detailed logging and monitoring for unauthorized access attempts to sensitive plugin files

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel → Plugins → Webpushr Web Push Notifications → Version number. If version is 4.38.0 or lower, you are vulnerable.

Check Version:

wp plugin get webpushr-web-push-notifications --field=version

Verify Fix Applied:

After updating, verify plugin version shows > 4.38.0 in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unusual requests to webpushr plugin endpoints
  • Multiple failed access attempts to sensitive plugin files
  • Requests containing suspicious parameters targeting plugin functionality

Network Indicators:

  • Unusual traffic patterns to /wp-content/plugins/webpushr-web-push-notifications/
  • Requests attempting to access sensitive plugin files directly

SIEM Query:

source="web_server" AND (uri_path="/wp-content/plugins/webpushr-web-push-notifications/" OR user_agent CONTAINS "scanner" OR response_code=200 AND uri_path CONTAINS "webpushr")

🔗 References

📤 Share & Export