Advanced Order Export For WoocommerceWordPress extension · Algolplus
CVE-2021-27349
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 · uneditedAdvanced Order Export before 3.1.8 for WooCommerce allows XSS, a different vulnerability than CVE-2020-11727.
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 confidenceCross-Site Scripting (XSS) vulnerability in the Advanced Order Export plugin for WooCommerce affecting versions prior to 3.1.8. The vulnerability allows remote attackers to inject malicious scripts through unsanitized input fields within the plugin's export functionality.
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 Order Export For WoocommerceWordPress extension
< 3.1.8CVSS 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.
-
Confirm plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Advanced Order Export For Woocommerce' by AlgolplusAffected if The plugin appears in the installed plugins list
-
Identify installed versionIn the Plugins list, find the plugin and note the version number displayed below the plugin name, or click the plugin to view its details and versionAffected if Version is less than 3.1.8 or no version is displayed and the plugin name matches 'Advanced Order Export For Woocommerce'
-
Verify export functionality is activeNavigate to WooCommerce > Export Orders in the admin panel to confirm the export feature is accessible and configuredAffected if The export page loads and accepts input, indicating the vulnerable feature is enabled
-
Check for suspicious export activityReview recent export logs or check exported files for unexpected script tags or unusual content in order data fieldsAffected if Exported files contain script tags or unexpected HTML/JavaScript content in fields that should contain order data
The environment is affected if the Advanced Order Export For Woocommerce plugin is installed with a version lower than 3.1.8 and the export functionality is accessible and operational.
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 data3.1.8
Update Advanced Order Export plugin to version 3.1.8 or later to patch the XSS vulnerability. If immediate update is not possible, disable the plugin until a patch can be applied.
Fix this in Advanced Order Export For Woocommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27349 — 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-2021-27349 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