CVE-2026-32459
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 flycart UpsellWP checkout-upsell-and-order-bumps allows Blind SQL Injection.This issue affects UpsellWP: from n/a through <= 2.2.4.
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 confidenceA blind SQL injection vulnerability exists in the flycart UpsellWP plugin (checkout-upsell-and-order-bumps functionality) affecting versions up to and including 2.2.4. The vulnerability allows attackers to inject malicious SQL queries through unsanitized input parameters, potentially enabling data exfiltration from the database.
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 UpsellWP plugin installationIdentify the plugin directory on the web server, typically under wp-content/plugins/, looking for directories named 'checkout-upsell-and-order-bumps', 'upsellwp', or similar naming patterns associated with the flycart UpsellWP plugin.Affected if The plugin directory exists on the server and contains UpsellWP files.
-
Determine the installed plugin versionOpen the main plugin file (usually the primary PHP file in the plugin root) or the readme.txt file within the plugin directory and locate the version declaration or header comment specifying the version number.Affected if The version number found is 2.2.4 or lower.
-
Verify the checkout-upsell-and-order-bumps feature is activeCheck the WordPress admin plugin settings page for UpsellWP, or inspect the database wp_options table for records related to 'upsellwp' or 'checkout_upsell' configuration that indicate the feature is enabled.Affected if The checkout-upsell-and-order-bumps functionality is enabled in the plugin settings or actively used on the site.
-
Identify SQL interaction points in the vulnerable code pathSearch plugin PHP files within the checkout-upsell-and-order-bumps directory for direct database query construction (such as $wpdb->prepare with unsanitized variables, direct $wpdb->query calls, or raw SQL concatenation) that handle user-supplied input from request parameters.Affected if Code exists that processes request parameters (GET, POST, or cookie values) directly into SQL queries without using prepared statements or input sanitization functions.
A user is affected if the UpsellWP plugin is installed with version 2.2.4 or lower, the checkout-upsell-and-order-bumps feature is active, and unsanitized user input flows into SQL query execution within that feature's code paths.
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 dataUpgrade to a patched version of UpsellWP once available, or apply input validation and parameterized queries (prepared statements) to all database interactions within the vulnerable checkout-upsell-and-order-bumps code paths.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32459 — 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-2026-32459 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