CVE-2026-7562 MEDIUM

CVE-2026-7562: WP-Redirection <= 1.0.3 - Cross-Site Request Forgery to Settings Update

Vendor Phkcorp2005
Product WP-Redirection
Weakness CWE-352 · CSRF
Published May 12, 2026
Last update May 12, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

WP-Redirection versions 1.0.3 and earlier are vulnerable to cross-site request forgery (CSRF) attacks. An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the site without the administrator's knowledge or consent. The vulnerability requires the victim to visit the attacker's page while authenticated.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on the site by tricking an authenticated admin into visiting a malicious webpage.

Potential impact on your site

04Site Impact

An attacker can modify site settings or data through a logged-in admin's browser without their awareness.

Conditions required to exploit

05Prerequisites

Site admin must be logged in and visit an attacker-controlled page; no special privileges required.

Key dates

06Disclosure timeline

May 12, 2026 CVE published
May 12, 2026 Record updated

Related vulnerabilities

08Related CVE