dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-10040

HIGH · 7.7 CVSS v3.1 Published 2025-09-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/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 Import – Ultimate CSV XML Importer for WordPress plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'get_ftp_details' AJAX action in all versions up to, and including, 7.27. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve a configured set of SFTP/FTP credentials.

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 Import plugin exposes a 'get_ftp_details' AJAX action that returns stored SFTP/FTP credentials without verifying user permissions. Any authenticated user with Subscriber-level access can invoke this action and retrieve sensitive connection credentials, representing a broken access control vulnerability.

MitigationUpgrade to version 7.28 or later which includes proper capability checks. Until then, consider restricting the Subscriber role or disabling the plugin if not needed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checks

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

  1. Check WP Import plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'WP Import' or check the plugin's main file header for 'Version'
    Affected if Version is below 7.28 (the fixed version)
  2. Verify Subscriber-level users exist
    In WordPress admin, go to Users and check for any users with the 'Subscriber' role assigned
    Affected if At least one user with Subscriber role exists in the system
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify WP Import is currently activated
    Affected if The WP Import plugin is active and version is below 7.28
  4. Test AJAX endpoint accessibility (optional)
    If you have CLI access, inspect the plugin code for the 'get_ftp_details' AJAX action handler and verify it lacks capability checks; alternatively, use a browser developer tools to check if a logged-in Subscriber user can access wp-admin/admin-ajax.php?action=get_ftp_details
    Affected if The AJAX action responds without requiring admin-level permissions

Your environment is affected if the WP Import plugin version is below 7.28, the plugin is active, and any user with Subscriber role exists in WordPress, allowing that low-privilege user to potentially retrieve stored FTP/SFTP credentials via the unprotected AJAX action.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 7.28 or later which includes proper capability checks. Until then, consider restricting the Subscriber role or disabling the plugin if not needed.

Recommended fix Moderate confidence

Upgrade to the latest version of the WP Import plugin (version > 7.27)

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'WP Import – Ultimate CSV XML Importer for WordPress' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the new version number is greater than 7.27
  6. 6. Confirm the plugin is functioning correctly by running a test import

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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