dbcve.org
Wp All ExportWordPress extension · Soflyy

CVE-2024-7425

HIGH · 7.2 CVSS v3.1 Published 2025-02-07
Fix available
A fix is available. Upgrade to 1.9.2 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 WP ALL Export Pro plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to improper user input validation and sanitization in all versions up to, and including, 1.9.1. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 confidence

The WP ALL Export Pro WordPress plugin versions up to 1.9.1 fails to properly validate and sanitize user input, allowing authenticated users with Shop Manager role or higher to modify arbitrary WordPress options. Attackers can change the default user registration role to Administrator and enable user registration, then register an administrative account to fully compromise the site.

MitigationUpdate WP ALL Export Pro to the latest version immediately. Review user accounts for unauthorized administrative users, change the default role back to a safe setting (e.g., Subscriber), and disable user registration if not needed. Audit the site for other privilege escalation vectors.

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
Wp All ExportWordPress extension
Affected:< 1.9.2

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Verify WP ALL Export Pro version
    Navigate to Plugins > Installed Plugins in WordPress admin, locate 'WP All Export Pro', and check the version number displayed. Alternatively, check the plugin's main PHP file header or version.php for the version constant.
    Affected if The installed version is 1.9.1 or lower (any version prior to 1.9.2).
  2. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that WP All Export Pro shows as 'Active'.
    Affected if The plugin is installed and active.
  3. Check if user registration is enabled
    Go to Settings > General in WordPress admin and locate the 'Membership' setting. Check if 'Anyone can register' is checked/enabled.
    Affected if User registration is enabled on the site.
  4. Inspect default user role setting
    Go to Settings > General in WordPress admin and locate the 'New User Default Role' dropdown. Note the selected role.
    Affected if The default role is set to 'Administrator'.
  5. Audit user accounts for unauthorized admins
    Go to Users > All Users in WordPress admin. Review the list for administrative accounts that you did not create or that are not recognized. Cross-reference user registration dates with the timeline of when this plugin was active.
    Affected if There are administrative users that were not intentionally created by site administrators.

You are affected if WP All Export Pro version 1.9.1 or lower is active AND user registration is enabled with Administrator as the default role, or if unauthorized admin accounts exist.

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.9.2 or later
Fixed in 1.9.2
Interim mitigation

Update WP ALL Export Pro to the latest version immediately. Review user accounts for unauthorized administrative users, change the default role back to a safe setting (e.g., Subscriber), and disable user registration if not needed. Audit the site for other privilege escalation vectors.

Recommended fix High confidence

WP ALL Export Pro version 1.9.2 or later

  1. Back up your WordPress site database and files before making any changes
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Find WP ALL Export Pro in the plugin list
  5. Click 'Update now' if an update is available, or manually download version 1.9.2 or later from a trusted source such as the official WP All Import website or wordpress.org repository
  6. Verify the plugin updated successfully to version 1.9.2 or higher
  7. Test that the plugin functionality remains working as expected

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

Fix this in Wp All Export Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7425 — 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-2024-7425 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