dbcve.org
CopifyWordPress extension

CVE-2022-1900

HIGH · 8.8 CVSS v3.1 Published 2022-06-13
Fix available
A fix is available. Upgrade to after 1.3.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Copify plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.3.0. This is due to missing nonce validation on the CopifySettings page. This makes it possible for unauthenticated attackers to update the plugins settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Copify WordPress plugin versions up to 1.3.0 lack nonce validation on the CopifySettings page, allowing unauthenticated attackers to forge administrative requests. This CSRF vulnerability enables attackers to modify plugin settings and inject malicious web scripts by tricking administrators into clicking crafted links.

MitigationUpdate the Copify plugin to a patched version beyond 1.3.0; if no patch exists, remove the plugin. Additionally, implement WordPress nonces on all settings forms and consider site-wide CSRF protections.

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
CopifyWordPress extension
Affected:<= 1.3.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Copify plugin installation status
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'Copify' or 'Copify Copify' to confirm whether the plugin is installed and active.
    Affected if The Copify plugin is present and activated in the WordPress installation.
  2. Identify installed Copify plugin version
    In the WordPress plugins list, locate the Copify plugin entry and read the version number displayed beneath the plugin name. Alternatively, check the plugin header in its main PHP file (typically in wp-content/plugins/copify/ or similar path) for the Version field.
    Affected if The installed version is 1.3.0 or lower.
  3. Locate CopifySettings page
    In WordPress admin, look for a settings page labeled 'Copify', 'CopifySettings', or similar under the Settings menu or as a dedicated plugin menu item. Note the URL path of this settings page.
    Affected if A Copify settings page exists and is accessible within the WordPress admin dashboard.
  4. Inspect settings form for nonce protection
    View the source code of the CopifySettings page (or the form HTML), then search for the presence of a nonce field (typically appears as wpnonce, _wpnonce, or similar naming convention) within the settings form. Check if the form includes security tokens that validate request origin.
    Affected if The settings form lacks a nonce field or token verification mechanism.

A user is affected if the Copify WordPress plugin is installed with version 1.3.0 or lower and its settings form lacks proper nonce validation.

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.

From vendor data
Upgrade available Upgrade to a release after 1.3.0
Interim mitigation

Update the Copify plugin to a patched version beyond 1.3.0; if no patch exists, remove the plugin. Additionally, implement WordPress nonces on all settings forms and consider site-wide CSRF protections.

Fix this in Copify Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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