CVE-2026-4071: CWE-352 Cross-Site Request Forgery (CSRF) in birdseedapp BirdSeed
The BirdSeed WordPress plugin is vulnerable to Cross-Site Request Forgery (CSRF) in all versions up to and including 2.2.0. The vulnerability arises from missing nonce validation in the birdseed_plugin_settings_page() function, which processes a 'birdseed_token' GET parameter and saves it without verifying the request's authenticity. This allows an attacker to trick an administrator into changing the plugin's token setting via a forged request.
AI Analysis
Technical Summary
CVE-2026-4071 describes a CSRF vulnerability in the BirdSeed WordPress plugin affecting all versions up to 2.2.0. The vulnerability is due to the lack of nonce validation in the birdseed_plugin_settings_page() function. This function accepts a 'birdseed_token' parameter via GET and updates the plugin's token setting in the database without verifying the request's origin or intent. Consequently, an unauthenticated attacker can cause an administrator to unknowingly change the plugin's token by tricking them into clicking a malicious link or performing a crafted request.
Potential Impact
An attacker can modify the BirdSeed token setting without authentication by exploiting the CSRF vulnerability. This could lead to unauthorized changes in plugin configuration, potentially impacting the plugin's intended functionality or security posture. There is no direct confidentiality or availability impact reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should avoid clicking untrusted links while logged into WordPress and consider restricting access to the plugin settings page. Implementing manual nonce validation or other CSRF protections in the plugin code can mitigate the risk.
CVE-2026-4071: CWE-352 Cross-Site Request Forgery (CSRF) in birdseedapp BirdSeed
Description
The BirdSeed WordPress plugin is vulnerable to Cross-Site Request Forgery (CSRF) in all versions up to and including 2.2.0. The vulnerability arises from missing nonce validation in the birdseed_plugin_settings_page() function, which processes a 'birdseed_token' GET parameter and saves it without verifying the request's authenticity. This allows an attacker to trick an administrator into changing the plugin's token setting via a forged request.
CVSS v3.1
Score 4.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-4071 describes a CSRF vulnerability in the BirdSeed WordPress plugin affecting all versions up to 2.2.0. The vulnerability is due to the lack of nonce validation in the birdseed_plugin_settings_page() function. This function accepts a 'birdseed_token' parameter via GET and updates the plugin's token setting in the database without verifying the request's origin or intent. Consequently, an unauthenticated attacker can cause an administrator to unknowingly change the plugin's token by tricking them into clicking a malicious link or performing a crafted request.
Potential Impact
An attacker can modify the BirdSeed token setting without authentication by exploiting the CSRF vulnerability. This could lead to unauthorized changes in plugin configuration, potentially impacting the plugin's intended functionality or security posture. There is no direct confidentiality or availability impact reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should avoid clicking untrusted links while logged into WordPress and consider restricting access to the plugin settings page. Implementing manual nonce validation or other CSRF protections in the plugin code can mitigate the risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-03-12T19:44:37.384Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1e9560e29bf47b50adbe6f
Added to database: 06/02/2026, 08:33:36 UTC
Last enriched: 06/09/2026, 09:53:30 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 42
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.