dbcve.org
Wp Content Copy Protection \& No Right ClickWordPress extension · Wp Buy

CVE-2022-23983

HIGH · 8.8 CVSS v3.1 Published 2022-02-21
Fix available
A fix is available. Upgrade to after 3.4.4 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
Cross-Site Request Forgery (CSRF) vulnerability leading to plugin Settings Update discovered in WP Content Copy Protection & No Right Click WordPress plugin (versions <= 3.4.4).

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

Cross-Site Request Forgery (CSRF) vulnerability in the WP Content Copy Protection & No Right Click WordPress plugin versions 3.4.4 and below allows attackers to trick authenticated administrators into unknowingly modifying plugin settings by crafting malicious requests that the vulnerable plugin accepts without proper origin verification.

MitigationUpdate the WP Content Copy Protection & No Right Click plugin to a version newer than 3.4.4, or disable the plugin until a patched version is 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
Wp Content Copy Protection \& No Right ClickWordPress extension
Affected:<= 3.4.4

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 the plugin is installed
    Check if the 'wp-content-copy-protection' or similar plugin directory exists in wp-content/plugins/
    Affected if Plugin directory is present in the WordPress plugins folder
  2. Check the installed plugin version
    Open the plugin's main PHP file or readme.txt and locate the Version header
    Affected if Version is 3.4.4 or lower
  3. Confirm WordPress admin access
    Verify you have administrator-level access to the WordPress dashboard
    Affected if You are logged in as an administrator and can access plugin settings
  4. Inspect plugin settings page for missing CSRF tokens
    Use browser developer tools to examine the plugin's settings form HTML; look for the presence of a nonce or CSRF token field in admin settings forms
    Affected if No nonce or CSRF token field is found in the plugin's admin settings forms

Your environment is affected if the WP Content Copy Protection & No Right Click plugin is installed with version 3.4.4 or lower and you have administrator access to the WordPress admin area.

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 3.4.4
Interim mitigation

Update the WP Content Copy Protection & No Right Click plugin to a version newer than 3.4.4, or disable the plugin until a patched version is available.

Fix this in Wp Content Copy Protection \& No Right Click Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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