
AI-Powered CVE Analysis for WordPress Plugins
We use AI to automate the differential analysis between vulnerable and patched plugin versions to understand and interpret the security issues. What we share here is research-grade proof of concept demonstrations that are then fed back into our endpoint firewall service.
WordPress Proof of Concepts
AI-assisted vulnerability analysis with PoC demonstration
2026-01-06
CVE-2025-11877: User Activity Log <= 2.2 – Unauthenticated Limited Options Update via Failed Login (user-activity-log)
The User Activity Log plugin is vulnerable to a limited options update in versions up to, and including, 2.2. The failed-login handler 'ual_shook_wp_login_failed' lacks a capability check and writes failed usernames directly into update_option() calls. This makes it possible for unauthenticated attackers to push select site options from 0 to a non-zero value, allowing them…
2026-01-06
CVE-2025-13496: Moosend Landing Pages <= 1.1.6 – Missing Authorization to Authenticated (Subscriber+) Option Deletion (moosend-landing-pages)
The Moosend Landing Pages plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the moosend_landings_auth_get function in all versions up to, and including, 1.1.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete the 'moosend_landing_api_key' option value.
2026-01-06
CVE-2025-13520: MTCaptcha WordPress Plugin <= 2.7.2 – Cross-Site Request Forgery to Settings Update (mtcaptcha)
The MTCaptcha WordPress Plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.7.2. This is due to missing or incorrect nonce validation on the settings update functionality. This makes it possible for unauthenticated attackers to update the plugin settings, including sensitive values like the private key, via a…
2026-01-06
CVE-2025-13493: Latest Registered Users <= 1.4 – Missing Authorization to Unauthenticated Sensitive Information Exposure via User Data Export (latest-registered-users)
The Latest Registered Users plugin for WordPress is vulnerable to unauthorized user data export in all versions up to, and including, 1.4. This is due to missing authorization and nonce validation in the rnd_handle_form_submit function hooked to both admin_post_my_simple_form and admin_post_nopriv_my_simple_form actions. This makes it possible for unauthenticated attackers to export complete user details (excluding…
2026-01-06
CVE-2025-13519: SVG Map Plugin <= 1.0.0 – Cross-Site Request Forgery to Settings Update and Stored Cross-Site Scripting (svg-map-by-saedi)
The SVG Map Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.0. This is due to missing or incorrect nonce validation on multiple AJAX actions including 'save_data', 'delete_data', and 'add_popup'. This makes it possible for unauthenticated attackers to update the plugin's settings, delete map data, and…
2026-01-06
CVE-2025-13527: xShare <= 1.0.1 – Cross-Site Request Forgery to 'rs_plugin_reset' Parameter (xshare)
The xShare plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.1. This is due to missing nonce validation on the 'xshare_plugin_reset()' function. This makes it possible for unauthenticated attackers to reset the plugin's settings via a forged request granted they can trick a site administrator into performing…
2026-01-06
CVE-2025-12030: ACF to REST API <= 3.3.4 – Insecure Direct Object Reference to Authenticated (Contributor+) ACF Field/Option Modification (acf-to-rest-api)
The ACF to REST API plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.3.4. This is due to insufficient capability checks in the update_item_permissions_check() method, which only verifies that the current user has the edit_posts capability without checking object-specific permissions (e.g., edit_post($id), edit_user($id), manage_options). This makes…
2026-01-06
CVE-2025-13521: WP Status Notifier <= 1.0 – Cross-Site Request Forgery to Settings Update (wp-change-status-notifier)
The WP Status Notifier plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the settings update functionality. This makes it possible for unauthenticated attackers to update the plugin settings via a forged request granted they can trick…
2026-01-06
CVE-2025-15000: Page Keys <= 1.3.3 – Authenticated (Administrator+) Stored Cross-Site Scripting via 'page_key' Parameter (page-keys)
The Page Keys plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘page_key’ parameter in all versions up to, and including, 1.3.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user…
2026-01-06
CVE-2025-15158: WP Enable WebP <= 1.0 – Authenticated (Author+) Arbitrary File Upload (wp-enable-webp)
The WP Enable WebP plugin for WordPress is vulnerable to arbitrary file uploads due to improper file type validation in the 'wpse_file_and_ext_webp' function in all versions up to, and including, 1.0. This makes it possible for authenticated attackers, with Author-level access and above, to upload arbitrary files on the affected site's server which may make…
How Atomic Edge Works
Simple Setup. Powerful Security.
Atomic Edge acts as a security layer between your website & the internet — inspecting, filtering, and blocking malicious traffic before it ever reaches
your application.
