CVE-2026-4071
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
References
- https://plugins.trac.wordpress.org/browser/birdseed/tags/2.2.0/birdseed.php#L42
- https://plugins.trac.wordpress.org/browser/birdseed/tags/2.2.0/birdseed.php#L43
- https://plugins.trac.wordpress.org/browser/birdseed/trunk/birdseed.php#L42
- https://plugins.trac.wordpress.org/browser/birdseed/trunk/birdseed.php#L43
- https://www.wordfence.com/threat-intel/vulnerabilities/id/236f5a78-435a-48d1-9dd7-c42a2155cb88?source=cve
CWEs
CWE-352
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.