dbcve.org
Store Exporter For WoocommerceWordPress extension · Visser

CVE-2016-10935

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-27
Fix available
A fix is available. Upgrade to 1.8.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The woocommerce-exporter plugin before 1.8.4 for WordPress has privilege escalation.

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 confidence

The woocommerce-exporter plugin before version 1.8.4 for WordPress contains a privilege escalation vulnerability that allows attackers to elevate their user permissions, likely by exploiting improper authorization checks in the plugin's functionality to gain administrative access.

MitigationUpdate the woocommerce-exporter plugin to version 1.8.4 or later to remediate this vulnerability. If updating is not possible, consider removing the plugin or implementing additional access controls at the web application firewall level.

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
Store Exporter For WoocommerceWordPress extension
Affected:< 1.8.4

CVSS 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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the woocommerce-exporter plugin files
    Check your WordPress installation's wp-content/plugins/ directory for a folder named 'woocommerce-exporter', 'woo-exporter', or 'visser-store-exporter'. Also check for any similarly named folder containing 'woo' and 'exporter' in the name.
    Affected if The plugin folder exists in the plugins directory
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically the file with the same name as the folder, e.g., woocommerce-exporter.php) and locate the 'Version:' header comment in the file's plugin metadata. Alternatively, check the readme.txt file in the plugin folder for the version number.
    Affected if The version number found is less than 1.8.4 or no version is displayed (indicating an old installation)
  3. Verify WordPress user role configuration
    Review your WordPress user roles in the admin dashboard under Users > Roles or use a database query to inspect the wp_usermeta table for any unusual role assignments that may indicate exploitation.
    Affected if Unexpected users have Administrator role or elevated permissions they should not possess
  4. Check for unauthorized admin accounts
    Query your WordPress database (wp_users and wp_usermeta tables) or inspect the Users admin page to list all user accounts with Administrator capabilities.
    Affected if There are administrator accounts you did not create or that belong to unknown users

You are affected if the woocommerce-exporter plugin is installed and its version is below 1.8.4, or if unauthorized admin accounts exist in your WordPress installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.8.4 or later
Fixed in 1.8.4
Interim mitigation

Update the woocommerce-exporter plugin to version 1.8.4 or later to remediate this vulnerability. If updating is not possible, consider removing the plugin or implementing additional access controls at the web application firewall level.

Recommended fix Moderate confidence

Store Exporter For WooCommerce 1.8.4

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Store Exporter For WooCommerce' plugin
  4. Click 'Update Now' if an update is available, or manually install version 1.8.4
  5. Verify the plugin is running version 1.8.4 or higher after updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Store Exporter For Woocommerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10935 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10935 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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