# CVE-2025-47513: WordPress Infocob CRM Forms plugin <= 2.4.0 - Arbitrary File Download vulnerability

> An attacker can exploit a path traversal flaw in the Infocob CRM Forms plugin to download arbitrary files from the server.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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:** 23 May 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-v6m7-qh5v-q2j5

## What is CVE-2025-47513?

CVE-2025-47513 is a medium-severity path traversal vulnerability in James Laforge Infocob CRM Forms, published on 23 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in James Laforge Infocob CRM Forms infocob-crm-forms allows Path Traversal.This issue affects Infocob CRM Forms: from n/a through <= 2.4.0.

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

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


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

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

## Is CVE-2025-47513 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47513 is a medium-severity path traversal vulnerability in James Laforge Infocob CRM Forms, published on 23 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-47513 in the wild and no public exploit code.

Affected product: James Laforge Infocob CRM Forms. 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-47513/ (Markdown: https://insights.sbomify.com/CVE-2025-47513/index.md)
```

## Sources

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

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