dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-39548

HIGH · 7.1 CVSS v3.1 Published 2025-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 A WP Life Right Click Disable OR Ban right-click-disable-or-ban allows Stored XSS.This issue affects Right Click Disable OR Ban: from n/a through <= 1.1.17.

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

A CSRF vulnerability in the WordPress 'Right Click Disable OR Ban' plugin (versions <= 1.1.17) allows authenticated administrators to be tricked into submitting crafted requests that inject malicious JavaScript (stored XSS) into plugin settings, which then executes when other admin users view those settings.

MitigationUpdate the plugin to the latest version once available. Review admin user accounts and plugin settings for unauthorized changes. Implement WordPress nonce verification on all plugin forms and admin actions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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. Confirm plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Right Click Disable OR Ban' in the list
    Affected if The plugin appears in the installed plugins list
  2. Identify installed version
    Click 'View Details' on the plugin row or check the plugin header comment in /wp-content/plugins/right-click-disable-or-ban/[main-file].php to find the version number
    Affected if Version number is 1.1.17 or lower
  3. Check plugin settings for unexpected content
    Navigate to the plugin's settings page (usually under Settings or a dedicated menu item) and inspect all input fields, textareas, and option values for suspicious JavaScript code, script tags, or encoded payloads
    Affected if Any settings contain script tags, javascript: URLs, onload/onerror attributes, or other XSS vectors
  4. Review plugin database options
    Access WordPress database (via phpMyAdmin or wp-cli) and query wp_options table for option_name containing 'right_click' or the plugin prefix; examine stored values for XSS payloads
    Affected if Stored option values contain HTML script tags or event handler attributes
  5. Check for unauthorized admin accounts
    Go to Users > All Users and verify no unexpected administrator accounts were added, especially those with suspicious usernames or email addresses
    Affected if New or unknown admin accounts exist that were not created by authorized personnel

A user is affected if the Right Click Disable OR Ban plugin is installed at version 1.1.17 or lower, or if plugin settings contain unexpected script tags or JavaScript code.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version once available. Review admin user accounts and plugin settings for unauthorized changes. Implement WordPress nonce verification on all plugin forms and admin actions.

Have this fixed 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 help mitigating

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-2025-39548 — 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-2025-39548 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