CVE-2025-67467
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 StellarWP GiveWP give allows Cross Site Request Forgery.This issue affects GiveWP: from n/a through <= 4.13.1.
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 GiveWP WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions, such as modifying donation settings or disbursing funds, by forging HTTP requests.
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.
-
Confirm GiveWP plugin is installedCheck the WordPress plugins directory for the give folder, or query the wp_options table for 'active_plugins' to see if GiveWP is listed among active plugins.Affected if GiveWP plugin is active on the WordPress site.
-
Identify GiveWP versionCheck the main plugin file (givewp.php or similar) in wp-content/plugins/give/ for the Version header comment, or look in the WordPress plugin repository metadata.Affected if The installed version matches or falls within the affected version range of the CVE.
-
Verify nonce presence in donation formsInspect key form files in the GiveWP plugin (such as donation forms, settings forms, and fund disbursement forms) and search for the presence of wp_nonce_field() or wp_create_nonce() function calls within these form definitions.Affected if The forms handling donation settings or fund disbursement lack nonce field generation.
-
Verify nonce validation on form processingExamine the PHP files that process form submissions (found in the includes directory) and check if they call wp_verify_nonce() or check_admin_referer() to validate the nonce before processing state-changing requests.Affected if Form processing handlers do not perform nonce verification.
-
Check AJAX action nonce verificationReview AJAX handlers in GiveWP (typically in includes/admin/class-ajax.php or similar) and verify that each admin-facing AJAX action calls wp_verify_nonce() or check_ajax_referer() before executing.Affected if AJAX actions that modify donation settings or disburse funds lack nonce validation.
A site is affected if GiveWP is installed and the plugin's forms or AJAX handlers processing administrative actions lack nonce verification, allowing attackers to forge requests on behalf of authenticated administrators.
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 (WordPress nonces) on all state-changing forms and AJAX actions, and verify these tokens on submission. Additionally, configure SameSite cookie attributes and implement Referer header validation.
- 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-67467 — 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-67467 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