Approved changes feed: RSS · Atom
cpe:2.3:a:birdseedapp:birdseed:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Birdseedapp (f54ade4e-05f2-5094-8ff8-4f1699a6c03b) |
|---|---|
| Product | Birdseed (f4fb02e2-0ae9-5c08-bb17-f31a7108621c) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-4071 |
vulnerable | 2026-06-08 08:05:12.565651 |
BirdSeed <= 2.2.0 - Cross-Site Request Forgery via BirdSeed Token Change
MEDIUM (4.3)
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.
Published: 2026-06-02T07:48:28.424Z
Updated: 2026-06-02T10:46:52.069Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.