CVE-2023-47547
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 WPFactory Products, Order & Customers Export for WooCommerce plugin <= 2.0.7 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 · high confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in the WPFactory Products, Order & Customers Export for WooCommerce plugin up to version 2.0.7. The vulnerability allows an attacker to inject malicious JavaScript code through unsanitized user input that gets reflected back in the HTTP response 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<= 2.0.7CVSS 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 the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Products, Order & Customers Export for WooCommerce' by WPFactory. Alternatively, check the /wp-content/plugins/ directory for a folder named similarly to 'export-order-customer-for-woocommerce' or containing 'wpfactory'.Affected if The plugin is present in the WordPress installation
-
Identify the installed versionIn WordPress admin, go to Plugins > Installed Plugins and click 'View Details' on the WPFactory export plugin. Note the version number displayed.Affected if The version number is 2.0.7 or lower
-
Verify plugin is accessible to unauthenticated usersAccess the site frontend and check if the plugin's export functionality or its endpoints are reachable without logging in. The vulnerability is unauthenticated (reflected XSS), so any page loading the plugin's reflected parameters could be exploited.Affected if The plugin is active and its functionality or query parameters are accessible to visitors without login
You are affected if the plugin version is 2.0.7 or lower AND the plugin is active and accessible on your website where attacker-supplied query parameters could be reflected in the HTTP response.
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.
dbcve · scopedUpdate the plugin to the latest version (beyond 2.0.7) which should contain proper input validation and output encoding. If immediate update is not possible, implement web application firewall (WAF) rules to block XSS payloads in query parameters.
2.0.8 or latest stable release
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'WPFactory Products, Order & Customers Export for WooCommerce'
- Check if the current version is 2.0.7 or lower
- If vulnerable, click 'Update Now' to install the latest version
- Alternatively, download the latest version from wordpress.org/plugins and upload it manually
- After update, verify the installed version is above 2.0.7
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47547 — 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-47547 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