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

CVE-2025-26545

HIGH · 7.1 CVSS v3.1 Published 2025-02-13
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 shisuh Related Posts Line-up-Exactly by Milliard related-posts-line-up-exactry-by-milliard allows Stored XSS.This issue affects Related Posts Line-up-Exactly by Milliard: from n/a through <= 0.0.22.

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 Related Posts Line-up-Exactly by Milliard WordPress plugin allows authenticated administrators to be tricked into storing malicious JavaScript payloads via forged requests. The lack of proper nonce validation on admin actions enables attackers to inject XSS that persists in the database and executes when other users view the affected content.

MitigationImplement nonce token validation for all admin-side actions and apply proper input sanitization and output escaping to prevent XSS. Update to a patched version if available.

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 installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, locate 'Related Posts Line-up-Exactly by Milliard' (also may appear as 'Related Posts by Milliard' or similar), and record the installed version number from the plugin description.
    Affected if The plugin is installed and the version cannot be confirmed as patched or is older than any available patched release.
  2. Identify vulnerable admin actions
    Access the plugin settings page under the WordPress admin menu (typically under Settings or a dedicated 'Related Posts' menu item). Identify any form actions or AJAX endpoints that modify plugin settings or post associations.
    Affected if The plugin settings page exists and accepts configuration changes without requiring explicit nonce verification in the request.
  3. Check for nonce implementation in plugin code
    If code access is available, examine the plugin PHP files for admin action handlers. Search for functions handling POST/GET requests (such as save_settings, update_options, or similar) and verify if they include nonce verification using wp_verify_nonce or check_admin_referer.
    Affected if Admin action handlers exist that process user input without calling nonce verification functions, creating the CSRF vector.
  4. Test for persistent XSS in plugin settings
    Using a test WordPress environment, log in as administrator, navigate to the plugin settings, and inspect form fields for any that accept and store custom content (such as custom CSS, custom templates, or content filters). Submit a test payload like <script>alert('XSS')</script> and verify if it is stored and reflected back without sanitization.
    Affected if Plugin settings fields store and display unsanitized user input, allowing stored XSS to persist in the database.
  5. Verify database storage of plugin data
    Inspect the WordPress database tables (typically wp_options or custom tables created by the plugin) for stored plugin configuration data. Check if content submitted through plugin settings is stored with raw HTML or JavaScript without encoding.
    Affected if Plugin configuration data containing HTML or script tags is stored in plaintext in the database, indicating lack of input sanitization.

The environment is affected if the Related Posts Line-up-Exactly by Milliard plugin is installed, has admin-accessible settings that accept user input, and lacks proper nonce validation on admin action handlers allowing stored XSS to persist.

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 nonce token validation for all admin-side actions and apply proper input sanitization and output escaping to prevent XSS. Update to a patched version if available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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