dbcve.org
CopymaticWordPress extension

CVE-2024-31351

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 1.7 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
Unrestricted Upload of File with Dangerous Type vulnerability in Copymatic Copymatic – AI Content Writer & Generator.This issue affects Copymatic – AI Content Writer & Generator: from n/a through 1.6.

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 Copymatic WordPress plugin (versions up to 1.6) contains an unrestricted file upload vulnerability allowing attackers to upload dangerous file types (such as malicious PHP scripts) directly to accessible web directories, potentially enabling remote code execution on the server.

MitigationImplement strict allowlist-based file type validation with MIME type and magic byte verification, store uploads outside webroot or disable script execution in upload directories, and add proper authentication/authorization checks on all upload endpoints.

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
CopymaticWordPress extension
Affected:< 1.7

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 Copymatic plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Copymatic' in the list, or check the /wp-content/plugins/ directory for a folder named 'copymatic'
    Affected if The Copymatic plugin folder exists in the WordPress plugins directory
  2. Identify the installed Copymatic version
    In WordPress admin, go to Plugins > Installed Plugins, find Copymatic, and note the version number displayed below the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/copymatic/readme.txt or copymatic.php for the 'Version:' field
    Affected if The installed version is lower than 1.7 (for example: 1.6, 1.5, 1.4, etc.)
  3. Confirm the upload functionality is accessible
    Check if the Copymatic plugin is activated in Plugins > Installed Plugins. Then, identify if the plugin exposes any upload endpoints by reviewing the plugin files in /wp-content/plugins/copymatic/ for form handlers or AJAX actions related to file upload (look for 'upload', 'file', or 'POST' handlers in PHP files)
    Affected if The plugin is active and contains code handling file uploads without apparent restrictions
  4. Inspect upload directories for suspicious files
    Check common WordPress upload directories (/wp-content/uploads/ and /wp-content/uploads/copymatic/ if it exists) for newly created files with executable extensions such as .php, .php5, .phtml, .phar, or .phpt. Use a file manager or run: find /wp-content/uploads/ -name "*.php" -o -name "*.php5" -o -name "*.phtml"
    Affected if Any PHP files or other executable scripts are found in the upload directories that were not intentionally placed there

You are affected if the Copymatic plugin version is below 1.7, the plugin is active, and unverified executable files exist in upload directories.

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

Implement strict allowlist-based file type validation with MIME type and magic byte verification, store uploads outside webroot or disable script execution in upload directories, and add proper authentication/authorization checks on all upload endpoints.

Recommended fix Moderate confidence

Copymatic version 1.7 or later

  1. Backup your Copymatic installation and database before performing any upgrade
  2. Download the latest version of Copymatic (version 1.7 or later) from the official vendor source
  3. Replace the existing Copymatic files with the new version files
  4. Verify that the application functions correctly after the upgrade
  5. Check that the file upload functionality now properly validates and restricts uploaded file types

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

Fix this in Copymatic Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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