dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-10313

HIGH · 7.2 CVSS v3.1 Published 2025-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The Find And Replace content for WordPress plugin for WordPress is vulnerable to unauthorized Stored Cross-Site Scripting and Arbitrary Content Replacement due to a missing capability check on the far_admin_ajax_fun() function in all versions up to, and including, 1.1. This makes it possible for unauthenticated attackers to inject arbitrary web scripts into pages that can make privilege escalation and malicious redirects possible.

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 Find And Replace WordPress plugin versions up to 1.1 contains a missing capability check on the far_admin_ajax_fun() AJAX function, allowing unauthenticated attackers to inject malicious scripts via stored XSS and perform arbitrary content replacement, potentially leading to privilege escalation and malicious redirects.

MitigationUpdate to a patched version of the plugin when available, or disable the plugin until a fix is released. Implement a WAF rule to block suspicious AJAX requests to the vulnerable endpoint as a temporary measure.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

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 plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for a 'find-and-replace' or similar named folder
    Affected if The Find And Replace plugin is present in the installation
  2. Identify installed version
    In WordPress admin > Plugins, find the Find And Replace plugin and read the version number displayed below the plugin name, or inspect the plugin's main PHP file header for the 'Version' tag
    Affected if The version is 1.1 or lower (including any 1.0.x versions)
  3. Confirm plugin is active
    Check the Plugins page in WordPress admin - the plugin must be activated for the vulnerability to be exploitable
    Affected if The plugin shows as 'Active' status
  4. Verify AJAX endpoint accessibility
    Check if the WordPress AJAX endpoint /wp-admin/admin-ajax.php responds to the 'far_admin_ajax_fun' action without authentication. This can be tested by sending a POST request to admin-ajax.php with parameter action=far_admin_ajax_fun - a response (even an error) indicates the function is hooked
    Affected if The endpoint responds without requiring login (the vulnerability requires no authentication)
  5. Inspect plugin code for missing capability check
    Locate the plugin's main PHP file and search for the function far_admin_ajax_fun(). Examine whether the function includes any current_user_can(), wp_verify_nonce(), or other authorization checks before performing the replace operations
    Affected if The function executes without any capability or nonce verification

A user is affected if the Find And Replace plugin version 1.1 or lower is installed, active, and the AJAX endpoint responds to far_admin_ajax_fun without authentication checks.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the plugin when available, or disable the plugin until a fix is released. Implement a WAF rule to block suspicious AJAX requests to the vulnerable endpoint as a temporary measure.

Recommended fix Moderate confidence

Upgrade to the latest available version of 'Find And Replace content for WordPress' plugin (version > 1.1)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Find And Replace content for WordPress' plugin
  4. Check the current installed version (if it shows 1.1 or lower, it is vulnerable)
  5. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org and upload it
  6. After updating, verify the new version number is greater than 1.1
  7. Test the plugin functionality to ensure it still works as expected

Generated from the published advisory — verify against the referenced sources before acting.

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-10313 — 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-10313 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