dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-1317

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 SQL Injection in all versions up to, and including, 7.37. This is due to insufficient escaping on the `file_name` parameter which is stored in the database during file upload and later used in raw SQL queries without proper sanitization. This makes it possible for authenticated attackers with Subscriber-level access or higher to append additional SQL queries into already existing queries via a malicious filename, which can be used to extract sensitive information from the database. The vulnerability can only be exploited when the 'Single Import/Export' option is enabled, and the server is running a PHP version < 8.0.

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

SQL injection vulnerability in the WP Import plugin where the file_name parameter is stored during upload and later used in unsanitized raw SQL queries. Authenticated attackers with Subscriber-level access can exploit this via malicious filenames to extract sensitive data from the database.

MitigationUpdate the plugin beyond version 7.37 to patch the SQL injection. Until then, disable the 'Single Import/Export' option and ensure PHP 8.0+ is running. Review database queries using the file_name parameter for proper escaping or prepared statements.

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

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

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

  1. Verify WP Import plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'WP Import' or 'WP Import Export' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wp-import' or similar.
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    In WordPress admin > Plugins, find WP Import and note the version number displayed. Compare this to the affected range: versions 7.37 and earlier are vulnerable.
    Affected if The installed version is 7.37 or lower
  3. Determine if Single Import/Export option is enabled
    Go to WP Import plugin settings in WordPress admin. Look for an option labeled 'Single Import/Export' or similar. Check if it is toggled ON or enabled.
    Affected if Single Import/Export is enabled (this increases exposure to the vulnerability)
  4. Inspect database for suspicious file_name entries
    Query the WordPress database tables where WP Import stores upload metadata (commonly postmeta or a custom import table). Look for file_name values containing SQL syntax like quotes, UNION, SELECT, or unusual characters.
    Affected if Records exist with file_name values containing SQL injection patterns or unexpected special characters

A user is affected if the WP Import plugin is installed with version 7.37 or lower and the Single Import/Export feature is enabled, allowing authenticated subscribers to inject malicious SQL via filenames.

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

Update the plugin beyond version 7.37 to patch the SQL injection. Until then, disable the 'Single Import/Export' option and ensure PHP 8.0+ is running. Review database queries using the file_name parameter for proper escaping or prepared statements.

Recommended fix Moderate confidence

Plugin version 7.38 or later (WP Import – Ultimate CSV XML Importer for WordPress)

  1. Check current plugin version in WordPress admin under Plugins > Installed Plugins
  2. If version is 7.37 or earlier, navigate to Plugins > Add New > Upload Plugin or check the WordPress plugin repository for version 7.38 or later
  3. Upload and install the updated plugin version
  4. Verify the upgrade was successful by confirming the new version number in the plugins list
  5. Ensure the 'Single Import/Export' option is disabled if not needed, as this is a required condition for exploitation
  6. Verify PHP version (if possible) - the vulnerability requires PHP < 8.0 to exploit, so upgrading PHP to 8.0+ would provide additional defense-in-depth
Caveat Standard plugin upgrade - review settings after upgrade to confirm import configurations are intact

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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