dbcve.org
Disable Right Click For WpWordPress extension · Disable Right Click For Wp Wordpress

CVE-2022-29427

HIGH · 8.8 CVSS v3.1 Published 2022-05-20
Fix available
A fix is available. Upgrade to after 1.1.6 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 in Aftab Muni's Disable Right Click For WP plugin <= 1.1.6 at WordPress.

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 'Disable Right Click For WP' WordPress plugin version 1.1.6 and below. Attackers can craft malicious requests that trick authenticated administrators into performing unintended actions like changing plugin settings.

MitigationUpdate the plugin to the latest patched version if available; if no patch exists, disable the plugin and replace with a maintained alternative. Ensure WordPress admin sessions implement anti-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
Disable Right Click For WpWordPress extension
Affected:<= 1.1.6

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. Check if Disable Right Click For WP plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Disable Right Click For WP' in the installed plugins list, or check the /wp-content/plugins/ directory for a folder containing 'disable-right-click-for-wp'
    Affected if Plugin is not present in the WordPress installation
  2. Verify the installed plugin version
    In WordPress admin > Plugins, click on the plugin details for 'Disable Right Click For WP' and read the version number, or open the main plugin PHP file and locate the 'Version' header in the plugin comment block
    Affected if Version is 1.1.6 or lower
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify the plugin shows 'Active' status. CSRF attacks require the plugin to be enabled to exploit the settings change vector
    Affected if Plugin is activated

You are affected if the Disable Right Click For WP plugin is installed, active, and running version 1.1.6 or lower in your WordPress environment.

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.1.6
Interim mitigation

Update the plugin to the latest patched version if available; if no patch exists, disable the plugin and replace with a maintained alternative. Ensure WordPress admin sessions implement anti-CSRF protections.

Fix this in Disable Right Click For Wp 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-29427 — 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-29427 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