# CVE-2025-15609: Fortis For WooCommerce < 1.3.1 - Sensitive API Key Disclosure

> Unauthenticated attackers can retrieve sensitive API keys to access customer PII and order data via the Fortis for WooCommerce plugin.

- **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:** 19 May 2026
- **Updated:** 19 May 2026
- **Also known as:** GHSA-4vhv-3qc3-cx8p

## What is CVE-2025-15609?

CVE-2025-15609 is a high-severity vulnerability in Unknown Fortis for WooCommerce, published on 19 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Fortis for WooCommerce WordPress plugin before 1.3.1 may leak sensitive API keys to unauthenticated attackers, allowing them to query Fortis' API and retrieve sensitive customer information, like past orders, PII, etc.

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


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

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

## Is CVE-2025-15609 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15609 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15609 is a high-severity vulnerability in Unknown Fortis for WooCommerce, published on 19 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15609 exists.

Affected product: Unknown Fortis for WooCommerce. 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-15609/ (Markdown: https://insights.sbomify.com/CVE-2025-15609/index.md)
```

## Sources

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

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