CVE-2025-31859
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Feedbucket Feedbucket – Website Feedback Tool feedbucket allows Cross Site Request Forgery.This issue affects Feedbucket – Website Feedback Tool: from n/a through <= 1.0.6.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Feedbucket WordPress plugin (version <= 1.0.6) allows attackers to trick authenticated users into performing unintended actions via malicious requests. The plugin lacks proper anti-CSRF token validation on its forms and AJAX actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Feedbucket plugin is installedLog into WordPress admin, go to Plugins > Installed Plugins, and search for 'Feedbucket'. Alternatively, check if the /wp-content/plugins/feedbucket/ directory exists.Affected if The Feedbucket plugin directory exists and the plugin is active in WordPress.
-
Verify the installed version numberIn WordPress admin, find Feedbucket in the plugins list and read the version number displayed. Alternatively, open /wp-content/plugins/feedbucket/feedbucket.php and check the 'Version:' header comment at the top of the file.Affected if The installed version is 1.0.6 or lower.
-
Inspect form files for missing nonce fieldsExamine the main plugin PHP files in /wp-content/plugins/feedbucket/ for HTML form definitions. Look for forms that submit to admin-post.php or similar endpoints without including a wp_nonce_field() call.Affected if Forms exist that do not contain a hidden nonce field (typically named '_wpnonce' or '_wp_token').
-
Check AJAX handlers for nonce verificationSearch the plugin files for add_action('wp_ajax_') or add_action('wp_ajax_nopriv_') calls. For each AJAX handler, verify that wp_verify_nonce() or check_ajax_referer() is called before processing the request.Affected if AJAX actions are registered but do not validate nonces before processing requests.
You are affected if the Feedbucket plugin (version 1.0.6 or lower) is active on your WordPress site and its forms or AJAX endpoints lack proper nonce validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens (nonces) on all form submissions and AJAX endpoints in the plugin, and validate these tokens server-side before processing any state-changing requests.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31859 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31859 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data