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

CVE-2025-23817

HIGH · 7.1 CVSS v3.1 Published 2025-01-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 mahadirz MHR-Custom-Anti-Copy mhr-custom-anti-copy allows Stored XSS.This issue affects MHR-Custom-Anti-Copy: from n/a through <= 2.0.

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

A CSRF vulnerability in the MHR-Custom-Anti-Copy WordPress plugin (versions up to 2.0) allows attackers to inject malicious JavaScript through stored XSS. By tricking an authenticated administrator into visiting a crafted link, attackers can persistently embed XSS payloads that execute when other users view affected content.

MitigationImplement WordPress nonces on all state-changing actions and apply proper output escaping when rendering user-supplied content to prevent stored XSS execution.

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. Identify if MHR-Custom-Anti-Copy plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'mhr-custom-anti-copy' or search the WordPress admin plugins list for 'MHR-Custom-Anti-Copy'
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress admin panel plugins list
  2. Determine the installed plugin version
    Open the main plugin file (typically mhr-custom-anti-copy.php) in the plugin folder and locate the 'Version' field in the plugin header comment at the top of the file
    Affected if The version number is 2.0 or lower, or if no version is explicitly listed (indicating it may be an unversioned release up to 2.0)
  3. Check for stored content or settings that accept user input
    Access the plugin settings page in the WordPress admin panel and review any fields where content can be saved (such as custom messages, labels, or protection settings)
    Affected if The plugin settings page contains input fields that save data to the WordPress database without visible nonce verification prompts
  4. Inspect how the plugin renders saved content on the frontend
    Examine the plugin PHP files for functions that retrieve and display saved settings or custom content (look for functions like get_option, get_post_meta, or database queries followed by echo or print statements)
    Affected if Saved plugin data is output using echo or print statements without passing through escaping functions such as esc_html(), esc_attr(), or wp_kses()
  5. Verify if state-changing actions use WordPress nonces
    Review the plugin PHP source code for form submissions and AJAX handlers; look forwp_nonce_field(), wp_nonce_verify(), or check_admin_referer() calls in functions that modify plugin settings or content
    Affected if Form handlers or AJAX endpoints that save or modify plugin data lack nonce verification code or contain nonces that are not properly validated before processing

A user is affected if the MHR-Custom-Anti-Copy plugin version 2.0 or lower is installed and its settings or stored content are rendered without proper output escaping, allowing injected scripts to execute when viewed by other users.

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

Implement WordPress nonces on all state-changing actions and apply proper output escaping when rendering user-supplied content to prevent stored XSS execution.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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