CVE-2026-0702
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 · uneditedThe VidShop – Shoppable Videos for WooCommerce plugin for WordPress is vulnerable to time-based SQL Injection via the 'fields' parameter in all versions up to, and including, 1.1.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 confidenceThe VidShop WordPress plugin versions up to 1.1.4 contain a time-based SQL injection vulnerability in the 'fields' parameter. Unauthenticated attackers can inject arbitrary SQL queries due to insufficient input escaping and missing prepared statements in the database query logic, potentially allowing extraction of sensitive data from the WordPress 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 VidShop plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a vidshop folderAffected if The VidShop plugin folder exists in the WordPress plugins directory
-
Check installed VidShop versionIn WordPress admin, go to Plugins > Installed Plugins > VidShop, or read the version from the plugin main PHP file header or readme.txtAffected if The installed version is 1.1.4 or any version lower than 1.1.4
-
Verify the plugin is activeCheck WordPress admin > Plugins > Installed Plugins to confirm VidShop shows as ActiveAffected if The VidShop plugin is currently activated on the WordPress site
-
Confirm the vulnerable endpoint is accessibleIdentify if the plugin exposes any public-facing endpoints that accept a fields parameter; check plugin PHP files for $_GET or $_REQUEST handling of the fields parameterAffected if The plugin processes user input through the fields parameter without proper preparation
A WordPress site with VidShop plugin version 1.1.4 or lower that has the plugin activated and processes the fields parameter in database queries is affected by this unauthenticated SQL injection vulnerability.
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 VidShop plugin to a version newer than 1.1.4 once available, or implement a WAF rule to block SQL injection attempts on the 'fields' parameter as a temporary compensating control until the vendor releases a patch.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0702 — 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-0702 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