# CVE-2025-10723: PixelYourSite < 11.1.2 - Admin+ LFI

> Administrators can exploit unvalidated URL parameters to perform Local File Inclusion attacks in the PixelYourSite WordPress plugin.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2025
- **Updated:** 9 Jan 2026
- **Also known as:** GHSA-259w-3jff-442h

## What is CVE-2025-10723?

CVE-2025-10723 is a low-severity path traversal vulnerability in Unknown PixelYourSite, published on 24 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The PixelYourSite  WordPress plugin before 11.1.2 does not validate some URL parameters before using them to generate paths passed to function/s, allowing any admins to perform LFI attacks

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2025-10723 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10723 is a low-severity path traversal vulnerability in Unknown PixelYourSite, published on 24 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10723 exists.

Affected product: Unknown PixelYourSite. 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-10723/ (Markdown: https://insights.sbomify.com/CVE-2025-10723/index.md)
```

## Sources

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

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