CVE-2025-22347
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 bannersky BSK Forms Blacklist bsk-gravityforms-blacklist allows Blind SQL Injection.This issue affects BSK Forms Blacklist: from n/a through <= 3.9.
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 · high confidenceCSRF vulnerability in BSK Forms Blacklist plugin for Gravity Forms allows attackers to trick authenticated administrators into executing malicious requests that lead to blind SQL injection. The lack of proper CSRF protection on admin actions enables attackers to inject SQL payloads through crafted form submissions.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/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 BSK Forms Blacklist plugin is installedNavigate to WordPress admin dashboard > Plugins and look for 'BSK Forms Blacklist' or 'BSK Forms Blacklist for Gravity Forms' in the installed plugins listAffected if The plugin appears in the installed plugins list
-
Identify the installed plugin versionIn WordPress admin > Plugins > BSK Forms Blacklist, click on the plugin name to view the version number displayed in the plugin detailsAffected if A version number is displayed and can be compared to any official advisory version range
-
Check for CSRF protection on admin formsInspect the plugin source code in wp-content/plugins/ directory for admin action forms (typically in admin/ folder). Look for wp_nonce_field, wp_nonce_url, or check_admin_referer calls in forms that handle blacklist settingsAffected if Admin forms that modify blacklist entries lack nonce/token validation (no wp_nonce_field or check_admin_referer found)
-
Verify database query implementationExamine PHP files in the plugin directory that handle database operations (look for $wpdb->prepare, $wpdb->query with parameterized queries, or direct variable interpolation in SQL statements)Affected if Database queries use string concatenation or interpolation without $wpdb->prepare or similar parameterization
You are affected if the BSK Forms Blacklist plugin is installed AND admin forms lack CSRF nonce protection AND database queries do not use prepared statements.
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 admin-facing forms and actions, and use parameterized queries or prepared statements for all database interactions to prevent SQL injection.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22347 — 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-22347 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