CVE-2026-31920
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 Devteam HaywoodTech Product Rearrange for WooCommerce products-rearrange-woocommerce allows Blind SQL Injection.This issue affects Product Rearrange for WooCommerce: from n/a through <= 1.2.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 · high confidenceA blind SQL injection vulnerability exists in the Product Rearrange for WooCommerce plugin (versions <= 1.2.2). The vulnerability allows attackers to inject malicious SQL commands through unsanitized input parameters, potentially enabling unauthorized database access, data exfiltration, or privilege escalation.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check if Product Rearrange for WooCommerce plugin is installedNavigate to WordPress admin > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'product-rearrange-for-woocommerce' or similar.Affected if The plugin folder exists in the WordPress plugins directory.
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate Product Rearrange for WooCommerce; the version number is displayed below the plugin name. Alternatively, check the main plugin PHP file for a 'Version' header comment.Affected if The displayed version is 1.2.2 or lower.
-
Verify WooCommerce is activeIn WordPress admin, confirm WooCommerce is installed and active, as this plugin is a WooCommerce extension.Affected if WooCommerce is installed and the Product Rearrange plugin is active.
-
Check for suspicious admin AJAX or frontend actionsReview the plugin source code (PHP files in the plugin folder) for database queries that use $_POST, $_GET, or $_REQUEST parameters without proper sanitization or prepare() statements.Affected if The plugin contains SQL queries that incorporate user input directly without parameterized queries.
You are affected if Product Rearrange for WooCommerce plugin is installed with version 1.2.2 or lower and contains unsanitized SQL query code.
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 dataUpdate the plugin to the latest patched version once released. Until a patch is available, implement Web Application Firewall (WAF) rules to block SQL injection payloads and restrict admin access to trusted users only.
- 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-2026-31920 — 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-31920 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