# CVE-2026-13700: WooMS <= 9.14 - Unauthenticated Server-Side Request Forgery and Sensitive Information Disclosure

> Unauthenticated attackers can perform SSRF and disclose integration credentials in WooMS when the data-sync feature is enabled.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 17 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-3wqr-pcph-pf9p

## What is CVE-2026-13700?

CVE-2026-13700 is a medium-severity server-side request forgery vulnerability in Unknown WooMS, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WooMS WordPress plugin through 9.14 does not validate a user-supplied URL before using it in a server-side request and attaches stored third-party integration credentials to every such request, allowing unauthenticated attackers to perform Server-Side Request Forgery and to disclose the configured integration credentials when the relevant data-sync feature is enabled.

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

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


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

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

## Is CVE-2026-13700 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13700 is a medium-severity server-side request forgery vulnerability in Unknown WooMS, published on 17 Aug 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-13700 in the wild and no public exploit code.

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

## Sources

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

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