Additional Order Filters For WoocommerceWordPress extension · Antonbond
CVE-2023-47690
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Anton Bond Additional Order Filters for WooCommerce plugin <= 1.10 versions.
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 confidenceReflected Cross-Site Scripting (XSS) vulnerability in the Anton Bond Additional Order Filters for WooCommerce plugin. The vulnerability allows unauthenticated attackers to inject malicious JavaScript through unsanitized user input that gets reflected in the web page without proper output encoding.
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
Additional Order Filters For WoocommerceWordPress extension
<= 1.10CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Check installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > locate 'Antonbond Additional Order Filters For Woocommerce' and read the version number displayed under the plugin nameAffected if The displayed version is 1.10 or lower
-
Verify plugin file versionAccess the plugin directory via FTP or file manager, open the main plugin file (typically additional-order-filters-for-woocommerce.php or similar) and locate the 'Version' header in the plugin commentsAffected if The Version header shows 1.10 or lower
-
Identify vulnerable filter parametersExamine the plugin's frontend-facing files (usually in /includes/ or /templates/ folders) for $_GET or $_POST parameters used in order filtering that are reflected in HTML output without sanitization functions like esc_html() or esc_attr()Affected if Parameters used for order filtering (such as search, filter, or order-related fields) are output directly to HTML without proper encoding
-
Test for reflected input in filter functionalityIf the plugin provides a frontend filter interface (usually on WooCommerce order listing pages), submit a test payload like <script>alert(1)</script> in available filter input fields and check if the payload executes or appears unescaped in the responseAffected if The submitted payload is reflected in the page source without being HTML-encoded (visible as literal <script> tags or unescaped quotes)
The environment is affected if the plugin version is 1.10 or lower AND the order filter functionality is active and accessible, allowing unsanitized user input to be reflected in the page output.
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 a version beyond 1.10 that contains the security fix, or implement proper input validation and output encoding on all user-supplied parameters within the plugin.
Fix this in Additional Order Filters For Woocommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47690 — 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-2023-47690 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