Export All Posts\, Products\, Orders\, Refunds \& UsersWordPress extension · Smackcoders
CVE-2023-45066
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in Smackcoders Export All Posts, Products, Orders, Refunds & Users.This issue affects Export All Posts, Products, Orders, Refunds & Users: from n/a through 2.4.1.
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 plugin's export functionality lacks proper authorization checks, allowing unauthenticated attackers to potentially export sensitive data including user information, orders, and other content managed by the plugin.
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
Export All Posts\, Products\, Orders\, Refunds \& UsersWordPress extension
<= 2.4.1CVSS 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.
-
Verify the plugin is installedCheck your WordPress plugins directory or WordPress admin panel under Plugins > Installed Plugins for 'Export All Posts, Products, Orders, Refunds & Users' by SmackcodersAffected if The plugin is present in the WordPress installation
-
Check the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and look at the version number displayed for the Export All plugin, or inspect the main plugin file header for the Version fieldAffected if The installed version is 2.4.1 or lower
-
Confirm the export functionality is accessibleAttempt to access the export endpoint directly via browser or curl: visit /wp-admin/admin-ajax.php?action=export_all_export (or similar export-related URL endpoints used by the plugin) without authenticationAffected if The export page or endpoint loads without requiring login credentials
-
Check for web server access controlsReview your web server configuration (nginx.conf, .htaccess, or Apache config) for any rewrite rules or access controls restricting the export functionality to authenticated users onlyAffected if No access restrictions are configured and the plugin export endpoint responds to unauthenticated requests
If the Smackcoders Export All plugin version 2.4.1 or lower is installed and its export functionality is accessible without authentication, the environment is affected by CVE-2023-45066.
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 to the latest version of the plugin (beyond 2.4.1) when available. Until then, restrict access to the export functionality via web server rules or disable the plugin if not actively needed.
Fix this in Export All Posts\, Products\, Orders\, Refunds \& Users
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-2023-45066 — 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-45066 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