Advanced Woo SearchWordPress extension
CVE-2020-12070
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 Advanced Woo Search plugin version through 1.99 for Wordpress suffers from a sensitive information disclosure vulnerability in every ajax search request via the sql field to includes/class-aws-search.php.
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 confidenceThe Advanced Woo Search plugin for WordPress versions through 1.99 contains a sensitive information disclosure vulnerability in ajax search requests via the 'sql' parameter in includes/class-aws-search.php. This allows attackers to potentially access sensitive database information through manipulation of the sql field.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Advanced Woo SearchWordPress extension
<= 1.99CVSS 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.
-
Identify installed plugin versionIn WordPress admin dashboard, go to Plugins > Advanced Woo Search and check the version number displayed, or inspect the plugin header in file /wp-content/plugins/advanced-woo-search/includes/class-aws-search.php for the Version tagAffected if The installed version is 1.99 or lower (any version through 1.99 is affected)
-
Locate vulnerable fileVerify the presence of /wp-content/plugins/advanced-woo-search/includes/class-aws-search.php in the WordPress installationAffected if The file exists and is readable, indicating the plugin is installed with vulnerable code
-
Confirm ajax search functionality is activeCheck WordPress configuration for active ajax endpoints, typically accessible at /wp-admin/admin-ajax.php, and verify the advanced-woo-search plugin ajax handlers are registeredAffected if The site has ajax functionality enabled and the plugin is active, allowing the sql parameter to be manipulated in search requests
-
Inspect search parameter handlingReview the class-aws-search.php file for code that processes the 'sql' parameter in search queries, looking for unsanitized input passed to database queriesAffected if The code contains direct use of the sql parameter in SQL queries without proper parameterization or validation
The environment is affected if the Advanced Woo Search plugin version 1.99 or lower is installed and the ajax search functionality is enabled, allowing unauthenticated attackers to inject malicious SQL via the sql parameter.
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 Advanced Woo Search plugin to a patched version immediately. If no patched version is available, disable the plugin or implement WAF rules to block malicious sql parameter manipulation in ajax requests.
Fix this in Advanced Woo Search
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12070 — 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-2020-12070 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