# CVE-2025-62112: WordPress Import into Easy Property Listings plugin <= 2.2.1 - Cross Site Request Forgery (CSRF) vulnerability

> Attackers can trick authenticated users into performing unintended actions in the Import into Easy Property Listings WordPress plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:** 28 Apr 2026
- **Also known as:** GHSA-8hj8-8wm2-wh7h

## What is CVE-2025-62112?

CVE-2025-62112 is a medium-severity vulnerability in Merv Barrett Import into Easy Property Listings, 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

Cross-Site Request Forgery (CSRF) vulnerability in Merv Barrett Import into Easy Property Listings easy-property-listings-xml-csv-import allows Cross Site Request Forgery.This issue affects Import into Easy Property Listings: from n/a through <= 2.2.1.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2025-62112 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-62112 is a medium-severity vulnerability in Merv Barrett Import into Easy Property Listings, 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: There is no known exploitation of CVE-2025-62112 in the wild and no public exploit code.

Affected product: Merv Barrett Import into Easy Property Listings. 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-62112/ (Markdown: https://insights.sbomify.com/CVE-2025-62112/index.md)
```

## Sources

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

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