# CVE-2025-60201: WordPress WP Customer Area plugin <= 8.3.5 - Local File Inclusion vulnerability

> Attackers can exploit a local file inclusion vulnerability in the WP Customer Area plugin to read sensitive files or execute arbitrary code.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 6 Nov 2025
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-h6c4-8h46-gcfm

## What is CVE-2025-60201?

CVE-2025-60201 is a high-severity path traversal vulnerability in aguilatechnologies WP Customer Area, published on 6 Nov 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

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in aguilatechnologies WP Customer Area customer-area allows PHP Local File Inclusion.

This issue affects WP Customer Area: before 8.3.4.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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


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

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

## Is CVE-2025-60201 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60201 is a high-severity path traversal vulnerability in aguilatechnologies WP Customer Area, published on 6 Nov 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: There is no known exploitation of CVE-2025-60201 in the wild and no public exploit code.

Affected product: aguilatechnologies WP Customer Area. 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-60201/ (Markdown: https://insights.sbomify.com/CVE-2025-60201/index.md)
```

## Sources

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

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