CVE-2026-4071 BirdSeed <= 2.2.0 - Cross-Site Request Forgery via BirdSeed Token Change
Unauthenticated attackers can trick administrators into changing the BirdSeed token setting via a forged request, compromising plugin configuration integrity.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-4071?
CVE-2026-4071 is a medium-severity vulnerability in birdseedapp BirdSeed, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-352
Which versions are affected by CVE-2026-4071?
How do I fix CVE-2026-4071?
No fix has been published for CVE-2026-4071 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-4071 being exploited?
There is no known exploitation of CVE-2026-4071 in the wild and no public exploit code.
Sources
Also known as GHSA-7cjh-gmfx-r7gg.