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

CVE-2025-23818

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 pyko More Link Modifier more-link-modifier allows Stored XSS.This issue affects More Link Modifier: from n/a through <= 1.0.3.

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

The pyko More Link Modifier WordPress plugin (versions <= 1.0.3) contains a Cross-Site Request Forgery (CSRF) vulnerability that allows attackers to inject malicious JavaScript code via Stored XSS. Attackers can exploit this by tricking authenticated administrators into visiting a crafted page or clicking a malicious link, causing the malicious script to be stored in the plugin's settings and executed when other users access the affected functionality.

MitigationUpdate to a patched version of More Link Modifier once available, or apply CSRF tokens (nonces) to all state-changing operations in the plugin and implement proper input sanitization to prevent XSS. Until patched, avoid clicking untrusted links while logged into the WordPress admin.

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 plugin files
    Check if the plugin exists in your WordPress installation at wp-content/plugins/more-link-modifier/ or similar path containing 'pyko' and 'more-link-modifier' in the name
    Affected if The plugin directory exists in your wp-content/plugins folder
  2. Determine the installed version
    Open the main plugin PHP file (usually more-link-modifier.php) and look for the version comment or header field, such as 'Version: 1.0.3'
    Affected if The reported version number is 1.0.3 or lower (e.g., 1.0.2, 1.0.1, 1.0.0)
  3. Verify plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and check if More Link Modifier is activated, or query the wp_options table for active_plugins
    Affected if The plugin shows as 'Active' in the WordPress plugins list
  4. Inspect plugin settings for injected scripts
    Query the WordPress database: SELECT * FROM wp_options WHERE option_name LIKE '%more_link_modifier%' OR option_name LIKE '%pyko%'; examine the option_value field for script tags, javascript:, or HTML attributes like onload/onerror
    Affected if The plugin settings contain raw <script> tags, javascript: URIs, or event handler attributes (onclick, onload, onerror) without proper escaping

You are affected if the pyko More Link Modifier plugin is installed at version 1.0.3 or below, is currently active, and its settings contain unsanitized JavaScript or script tags.

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 a patched version of More Link Modifier once available, or apply CSRF tokens (nonces) to all state-changing operations in the plugin and implement proper input sanitization to prevent XSS. Until patched, avoid clicking untrusted links while logged into the WordPress admin.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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