dbcve.org
CopymaticWordPress extension

CVE-2024-35716

HIGH · 8.8 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 2.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in Copymatic Copymatic – AI Content Writer & Generator.This issue affects Copymatic – AI Content Writer & Generator: from n/a through 1.9.

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

Missing Authorization vulnerability in the Copymatic WordPress plugin allows unauthenticated or low-privilege users to access sensitive functionality or perform actions that should require higher privileges. This broken access control vulnerability has a CVSS base score of 8.8 (HIGH), indicating significant potential for confidentiality and integrity impact.

MitigationImplement proper capability checks and permission verification using WordPress current_user_can() and nonce validation on all sensitive functions and AJAX endpoints. Update to the latest plugin version if available.

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:< 2.0

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate Copymatic plugin installation
    Check for the Copymatic plugin directory at wp-content/plugins/copymatic/ or search for 'copymatic' in the WordPress plugins admin panel under Plugins > Installed Plugins
    Affected if The plugin directory exists or the plugin appears in the WordPress admin plugins list
  2. Determine installed plugin version
    Open the plugin's main PHP file (usually copymatic.php) in wp-content/plugins/copymatic/ and look for the 'Version' header in the plugin comments, or check the Version field in the WordPress plugins admin list
    Affected if The reported version number is less than 2.0 (for example, 1.x.x or any version below 2.0)
  3. Inspect AJAX endpoints for access control
    Examine the plugin's PHP files for AJAX handlers (search for 'add_action' with 'wp_ajax_' or 'wp_ajax_nopriv_') and verify if they include capability checks using current_user_can() before executing sensitive operations
    Affected if AJAX endpoints exist that lack current_user_can() capability checks or nonce validation
  4. Check for unprotected sensitive functions
    Review the plugin source code for functions that perform sensitive operations (content generation, user data access, settings modifications) and verify they include permission verification checks
    Affected if Sensitive functions can be invoked without proper WordPress capability verification

You are affected if the Copymatic plugin is installed and its version is below 2.0, as the missing authorization vulnerability exists in all prior versions.

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

Implement proper capability checks and permission verification using WordPress current_user_can() and nonce validation on all sensitive functions and AJAX endpoints. Update to the latest plugin version if available.

Recommended fix High confidence

Copymatic version 2.0

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find Copymatic – AI Content Writer & Generator
  4. If an update is available, click 'Update Now' to upgrade to version 2.0
  5. If automatic update is not available, manually download version 2.0 from the official WordPress plugin repository or vendor site and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is running version 2.0 in the plugins list

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

Fix this in Copymatic 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 the upgrade done

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-2024-35716 — 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-35716 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