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

CVE-2025-25148

HIGH · 7.1 CVSS v3.1 Published 2025-02-07
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 ElbowRobo Read More Copy Link read-more-copy-link allows Stored XSS.This issue affects Read More Copy Link: from n/a through <= 1.0.2.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Read More Copy Link WordPress plugin (versions <=1.0.2) allows attackers to inject malicious JavaScript code through stored XSS. The plugin lacks proper CSRF protection, enabling attackers to trick authenticated administrators into unknowingly executing crafted requests that persist malicious scripts.

MitigationUpdate to the latest patched version of the Read More Copy Link plugin once released. Until then, implement web application firewall rules to block malicious requests and monitor for suspicious 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. Locate the Read More Copy Link plugin installation
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'read-more-copy-link', 'read-more-copy-link-wordpress', or similar variations containing the plugin files.
    Affected if The plugin folder exists on the server.
  2. Determine the installed plugin version
    Open the main plugin PHP file (usually read-more-copy-link.php) and locate the 'Version' header in the plugin comment block at the top of the file.
    Affected if The reported version number is 1.0.2 or lower.
  3. Verify if the plugin is active
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for Read More Copy Link in the list and check if it is activated.
    Affected if The plugin shows as Active in the WordPress admin.
  4. Confirm admin access is available
    Check if you have administrator-level access to the WordPress dashboard, as the CSRF attack requires tricking an authenticated administrator into executing a malicious request.
    Affected if Administrator credentials exist and the wp-admin area is accessible.

Your environment is affected if the Read More Copy Link plugin is installed, active on your WordPress site, and the version is 1.0.2 or lower.

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 to the latest patched version of the Read More Copy Link plugin once released. Until then, implement web application firewall rules to block malicious requests and monitor for suspicious admin actions.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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