The BirdSeed plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2.0. This is due to missing nonce validation in the birdseed_plugin_settings_page() function. The function processes the 'birdseed_token' GET parameter and saves it to the database via update_option() without verifying a nonce. This makes it possible for unauthenticated attackers to change the plugin's BirdSeed token setting via a forged request, granted they can trick a site administrator into performing an action such as clicking a link.
Metrics
Affected Vendors & Products
References
History
Tue, 02 Jun 2026 08:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The BirdSeed plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2.0. This is due to missing nonce validation in the birdseed_plugin_settings_page() function. The function processes the 'birdseed_token' GET parameter and saves it to the database via update_option() without verifying a nonce. This makes it possible for unauthenticated attackers to change the plugin's BirdSeed token setting via a forged request, granted they can trick a site administrator into performing an action such as clicking a link. | |
| Title | BirdSeed <= 2.2.0 - Cross-Site Request Forgery via BirdSeed Token Change | |
| Weaknesses | CWE-352 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: Wordfence
Published:
Updated: 2026-06-02T10:46:52.069Z
Reserved: 2026-03-12T19:44:37.384Z
Link: CVE-2026-4071
No data.
Status : Deferred
Published: 2026-06-02T09:16:16.377
Modified: 2026-06-02T13:03:31.153
Link: CVE-2026-4071
No data.
OpenCVE Enrichment
Updated: 2026-06-02T09:30:05Z