CVE-2025-49034
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Aman Funnel Builder by FunnelKit funnel-builder allows SQL Injection.This issue affects Funnel Builder by FunnelKit: from n/a through <= 3.10.2.
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 confidenceSQL Injection vulnerability in the Funnel Builder by FunnelKit WordPress plugin allows unauthenticated attackers to inject malicious SQL commands via improper neutralization of special elements in SQL queries.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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.
-
Locate the FunnelKit plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Funnel Builder by FunnelKit and read the version number from the plugin description. Alternatively, check the version in the plugin header file: wp-content/plugins/funnel-builder/funnel-builder.phpAffected if The displayed version is lower than 3.10.2 (for example, 3.10.1, 3.0.5, etc.)
-
Confirm the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify that Funnel Builder by FunnelKit shows as 'Active'Affected if The plugin is active and the version is below 3.10.2
-
Identify if the plugin handles user input via SQL queriesReview the plugin settings and any public-facing forms or endpoints (such as order tracking, checkout, or funnel submission pages) that accept user input. Check if these pages query the database using the plugin's functionalityAffected if The plugin processes user-submitted data (such as order IDs, emails, or form inputs) through SQL queries without visible prepared statement protection, and the version is vulnerable
-
Check for recent access logs indicating SQL injection attemptsReview web server access logs (Apache/nginx) for unusual SQL syntax in query parameters targeting FunnelKit-related URLs (typically under /wp-json/ or plugin-specific endpoints). Look for patterns like UNION SELECT, OR 1=1, or other SQL keywordsAffected if Such suspicious patterns appear in logs and the plugin version is below 3.10.2
The environment is affected if Funnel Builder by FunnelKit is installed, active, and running a version lower than 3.10.2.
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.
dbcve · scopedUpdate Funnel Builder by FunnelKit to the latest version (beyond 3.10.2) which should contain parameterized query fixes. If no patch is available, disable the plugin until a fix is released.
Funnel Builder by FunnelKit version 3.10.3 or later
- 1. Backup your WordPress database and files before making any changes.
- 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
- 3. Locate 'Funnel Builder by FunnelKit' (also known as Aman Funnel Builder).
- 4. If an update is available, click 'Update Now' to upgrade to the latest version.
- 5. Alternatively, download the latest version from the WordPress Plugin Repository or from FunnelKit's official website.
- 6. After updating, verify the plugin is running on version 3.10.3 or later.
- 7. Test your funnels and checkout flows to ensure the update did not break functionality.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49034 — 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-49034 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