# CVE-2025-3702: WordPress Melapress File Monitor plugin < 2.2.0 - Broken Access Control vulnerability

> Attackers can bypass access controls to read or modify file change monitoring data in the Melapress File Monitor WordPress plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-39j6-jjvv-95wr

## What is CVE-2025-3702?

CVE-2025-3702 is a medium-severity missing authorization vulnerability in Melapress File Monitor, published on 3 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization vulnerability in Melapress Melapress File Monitor website-file-changes-monitor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Melapress File Monitor: from n/a through < 2.2.0.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Melapress Melapress File Monitor.

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

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

## Is CVE-2025-3702 being exploited?

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

## Other vulnerabilities in Melapress File Monitor

- [CVE-2024-9879](https://insights.sbomify.com/CVE-2024-9879/): Website File Changes < 2.1.1 - Authenticated SQL Injection (medium 5.4)
- [CVE-2024-10009](https://insights.sbomify.com/CVE-2024-10009/): Website File Changes < 2.1.0 - Admin+ Authenticated SQL Injection (medium 4.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3702 is a medium-severity missing authorization vulnerability in Melapress File Monitor, published on 3 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3702 in the wild and no public exploit code.

Affected product: Melapress File Monitor. 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-3702/ (Markdown: https://insights.sbomify.com/CVE-2025-3702/index.md)
```

## Sources

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

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