# CVE-2025-14313: Advance WP Query Search Filter <= 1.0.10 - Reflected XSS via taxo_ajax

> Reflected XSS in Advance WP Query Search Filter allows attackers to execute scripts against admin users via the taxo_ajax parameter.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Dec 2025
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-h52r-r84q-8jgv

## What is CVE-2025-14313?

CVE-2025-14313 is a medium-severity cross-site scripting vulnerability in Unknown Advance WP Query Search Filter, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Advance WP Query Search Filter WordPress plugin through 1.0.10 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin

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


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

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

## Is CVE-2025-14313 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14313 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14313 is a medium-severity cross-site scripting vulnerability in Unknown Advance WP Query Search Filter, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14313 exists.

Affected product: Unknown Advance WP Query Search Filter. 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-14313/ (Markdown: https://insights.sbomify.com/CVE-2025-14313/index.md)
```

## Sources

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

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