dbcve.org
Csv Import \/ ExportWordPress extension · Ait Themes

CVE-2020-36849

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-12
Fix available
A fix is available. Upgrade to after 3.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 AIT CSV import/export plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the /wp-content/plugins/ait-csv-import-export/admin/upload-handler.php file in versions up to, and including, 3.0.3. This makes it possible for unauthorized attackers to upload arbitrary files on the affected sites server which may make remote code execution possible.

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 AIT CSV import/export WordPress plugin lacks file type validation in its upload handler (upload-handler.php), allowing attackers to upload arbitrary files including malicious executables. This enables remote code execution on affected WordPress installations.

MitigationUpdate the plugin to version 3.0.4 or later. If no patch is available, remove the plugin immediately. Consider deploying a WAF rule to block unauthorized file uploads as a compensating control.

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
Csv Import \/ ExportWordPress extension
Affected:<= 3.0.3

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.1/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. Verify the AIT CSV Import/Export plugin is installed
    Check the WordPress plugins directory for 'ait-themes-csv-import-export' folder or look for the plugin in wp-admin > Plugins
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    Locate the main plugin file (usually ait-csv-import-export.php or similar) and check the version header in the plugin comments, or view the plugin via wp-admin > Plugins and note the version displayed
    Affected if The version listed is 3.0.3 or lower
  3. Confirm the vulnerable upload-handler.php file exists
    Navigate to wp-content/plugins/[plugin-directory]/upload-handler.php and verify the file is present
    Affected if The file upload-handler.php exists in the plugin directory
  4. Check if the upload functionality is accessible
    Attempt to access the upload-handler.php directly via browser (e.g., yoursite.com/wp-content/plugins/[plugin]/upload-handler.php) or check if the endpoint responds to upload requests
    Affected if The upload-handler.php is accessible and processes requests without authentication errors

The environment is affected if the AIT CSV Import/Export plugin version 3.0.3 or lower is installed and the upload-handler.php file is present and accessible.

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 a release after 3.0.3
Interim mitigation

Update the plugin to version 3.0.4 or later. If no patch is available, remove the plugin immediately. Consider deploying a WAF rule to block unauthorized file uploads as a compensating control.

Recommended fix Moderate confidence
  1. Confirm the plugin is installed on your WordPress site
  2. If the plugin is no longer needed, deactivate and delete it entirely from wp-admin > Plugins
  3. If the plugin is required, search the WordPress plugin repository or contact the vendor (AIT Themes) for a patched version that includes proper file type validation
  4. Review wp-content/plugins/ait-csv-import-export/ directory for any suspicious uploaded files
  5. Consider implementing a Web Application Firewall (WAF) rule to block malicious file uploads to the uploads directory
  6. Monitor server access logs for POST requests to /wp-content/plugins/ait-csv-import-export/admin/upload-handler.php
Caveat No fixed version information available in the provided material; verify with vendor before upgrading

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

Fix this in Csv Import \/ Export Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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