# CVE-2025-10313: Find And Replace content for WordPress <= 1.1 - Missing Authorization to Unauthenticated Stored Cross-Site Scripting

> Unauthenticated attackers can inject scripts via missing authorization checks, enabling privilege escalation and malicious redirects in the Find And Replace content plugin.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-wg83-xjwq-wqrh

## What is CVE-2025-10313?

CVE-2025-10313 is a high-severity missing authorization vulnerability in jankimoradiya Find And Replace content for WordPress, published on 15 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-10313?


## How do I fix CVE-2025-10313?

No fix has been published for CVE-2025-10313 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10313 being exploited?

There is no known exploitation of CVE-2025-10313 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10313 and fix it if it is affected.

What it is: CVE-2025-10313 is a high-severity missing authorization vulnerability in jankimoradiya Find And Replace content for WordPress, published on 15 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10313 in the wild and no public exploit code.

Affected product: jankimoradiya Find And Replace content for WordPress. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10313/ (Markdown: https://insights.sbomify.com/CVE-2025-10313/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10313
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10313
- OSV: https://osv.dev/vulnerability/CVE-2025-10313

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10313/
Summaries are generated and may contain mistakes; the official description above is the record.