CVE-2026-7562 json
WP-Redirection <= 1.0.3 - Cross-Site Request Forgery to Settings Update
published 2026-05-12 5 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-29417
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
The WP-Redirection plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.0.3. This is due to the absence of a nonce field in the admin settings form and the lack of any nonce verification (via check_admin_referer() or wp_verify_nonce()) in the displayWPRedirectionManagementPage() function before processing POST requests that add, edit, or delete URL redirection rules. This makes it possible for unauthenticated attackers to trick a logged-in administrator into clicking a crafted link, causing the attacker to create, modify, or delete redirection records in the plugin's database table without the administrator's consent.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
Affected products
- phkcorp2005 WP-Redirection
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/15177d1b-ef48-49e3-9bd9-34262ed2c134?source=cve
- plugins.trac.wordpress.org /browser/wp-redirection/trunk/wp-redirection.php#L39
- plugins.trac.wordpress.org /browser/wp-redirection/tags/1.0.3/wp-redirection.php#L39
- plugins.trac.wordpress.org /browser/wp-redirection/trunk/wp-redirection.php#L219
- plugins.trac.wordpress.org /browser/wp-redirection/tags/1.0.3/wp-redirection.php#L219
Sources
- CVE List CVE-2026-7562
- NVD CVE-2026-7562
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.