SEO Redirection AJAX action exposes redirect rules to Subscribers
SEO Redirection Plugin before 9.19 registers the authenticated customUpdateRec AJAX action without a capability or nonce check. Any logged-in user, including a Subscriber, can POST action=customUpdateRec and an attacker-chosen ID to /wp-admin/admin-ajax.php. WPSR_customUpdateRec_callback() queries that row from the WP_SEO_Redirection table and returns redirect_from, redirect_to, redirect type, source, folder and destination settings, and enabled state as JSON. This permits low-privilege enumeration of configured redirect rules; practical sensitivity depends on the site's URLs.
- Component
- SEO Redirection Plugin
- Plugin slug
seo-redirection-plugin- Affected
- < 9.19
- Safe version
9.19- Published
- Aug 06, 2026
This CVE was published Aug 06, 2026 and is one of 3 known issues for this plugin.
Update, patch or deactivate.
Update SEO Redirection Plugin to 9.19 or later. Review low-privilege AJAX requests and ensure redirect source or destination URLs do not expose secrets or private administrative routes.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The SEO Redirection Plugin WordPress plugin before 9.19 does not perform a capability check in one of its authenticated AJAX actions, allowing any logged-in user such as a subscriber to read the site's configured 301 redirect rules, including their source and destination URLs.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N