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

CVE-2025-25123

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 xdark Easy Related Posts easy-related-posts allows Stored XSS.This issue affects Easy Related Posts: from n/a through <= 2.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 · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Easy Related Posts WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions. Combined with Stored XSS, malicious scripts can be injected through plugin settings and executed when viewed by other users.

MitigationAdd proper WordPress nonce verification to all admin actions and form submissions, plus implement output escaping when displaying related post 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. Verify Easy Related Posts plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Easy Related Posts', or check the /wp-content/plugins/ directory for the easy-related-posts folder
    Affected if The plugin is installed and active - proceed to version check
  2. Check installed plugin version
    In WordPress admin Plugins list, click on 'View Details' for Easy Related Posts to see the version number, or read version.php in the plugin directory
    Affected if Version is unknown, unpatched, or within the affected range - the vulnerability may be present
  3. Confirm admin access to plugin settings
    Navigate to the plugin settings page in WordPress admin (usually under Settings > Easy Related Posts or similar)
    Affected if The plugin settings page is accessible and contains forms for configuring related posts options
  4. Inspect plugin settings for unsanitized input storage
    Check the plugin's options in wp_options table (look for option_name containing 'easy_related_posts' or similar) using a database query or plugin like WP Data Access
    Affected if Settings contain user-supplied content that could include script tags without proper escaping - stored XSS may be possible

If Easy Related Posts plugin is installed, active, and accessible via admin settings without verified nonce tokens on form submissions, the environment is likely affected by this CSRF and stored XSS vulnerability.

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

Add proper WordPress nonce verification to all admin actions and form submissions, plus implement output escaping when displaying related post content to prevent stored XSS execution.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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