WP-Redirection <= 1.0.3 - Cross-Site Request Forgery to Settings Update
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| phkcorp2005 | WP-Redirection | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Phkcorp2005 | Wp-redirection |
|
||||||||
| Wordpress | Wordpress |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.132% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Phkcorp2005
Phkcorp2005 wp-redirection Wordpress Wordpress wordpress |
|
| Vendors & Products |
Phkcorp2005
Phkcorp2005 wp-redirection Wordpress Wordpress wordpress |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | WP-Redirection <= 1.0.3 - Cross-Site Request Forgery to Settings Update | |
| Weaknesses | CWE-352 | |
| References |
|
|
| Metrics |
cvssV3_1
|