# CVE-2026-6514: InfusedWoo Pro <= 5.1.2 - Unauthenticated Arbitrary File Read via 'url' Parameter

> Unauthenticated attackers can exploit an SSRF vulnerability in InfusedWoo Pro to read arbitrary files and interact with internal services.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-mh5f-f33c-v7q4

## What is CVE-2026-6514?

CVE-2026-6514 is a high-severity server-side request forgery vulnerability in InfusedWoo Pro, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The InfusedWoo Pro plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 5.1.2 via the popup_submit. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-6514?


## How do I fix CVE-2026-6514?

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

## Is CVE-2026-6514 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6514 and fix it if it is affected.

What it is: CVE-2026-6514 is a high-severity server-side request forgery vulnerability in InfusedWoo Pro, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6514 in the wild and no public exploit code.

Affected product: InfusedWoo Pro. 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-2026-6514/ (Markdown: https://insights.sbomify.com/CVE-2026-6514/index.md)
```

## Sources

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

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