Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-28570 – Unauthenticated Local File Inclusion – Vavo Core WordPress Plugin (≤ 2.3.0)

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-28570 is a high-severity (CVSS 8.1) Local File Inclusion (LFI) vulnerability affecting the Vavo Core WordPress plugin, developed by SpabRice, in versions 2.3.0 and earlier. The flaw allows an unauthenticated remote attacker to force the plugin to include and execute arbitrary local files on the server, without requiring any credentials or user interaction. Given the plugin’s role as a companion component for the Vavo WordPress theme, sites running the affected versions are exposed to potential information disclosure, denial of service, or full compromise depending on server configuration.

Technical details

  • Root cause: The plugin fails to properly control or sanitize a filename/path parameter used in a PHP include/require-style statement (CWE-98, "Improper Control of Filename for Include/Require Statement in PHP Program").
  • Trigger conditions: An attacker sends a crafted network request that manipulates the vulnerable parameter to point to an arbitrary local file path on the server’s filesystem.
  • Attack vector: Network-based (AV:N), exploitable without authentication (PR:N) and without any user interaction (UI:N). Attack complexity is rated High (AC:H), indicating some non-trivial conditions must be met to reliably exploit the flaw.
  • Impact: If successfully exploited, the vulnerability can lead to full compromise of confidentiality, integrity, and availability (C:H/I:H/A:H) — potentially exposing sensitive files, enabling code execution via inclusion of attacker-controllable files (e.g., uploaded files or log files), or crashing the affected site.

Affected software

  • Vavo Core (WordPress plugin) — all versions up to and including 2.3.0
  • Vendor: SpabRice

Severity

  • CVSS v3.1 Base Score: 8.1 (High)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Vavo Core to a version newer than 2.3.0 that resolves the local file inclusion issue. Verify the update directly with the plugin/theme vendor (SpabRice) before deploying to production.
  • If no patch is available: Temporarily deactivate the Vavo Core plugin until a fixed version can be confirmed and installed. Restrict direct network access to the WordPress admin and plugin endpoints via a web application firewall (WAF) or reverse proxy rule that blocks path-traversal and file-inclusion patterns (e.g., ../, php://, wrapper schemes) in request parameters.
  • Review web server and PHP configuration to disable dangerous features that amplify LFI impact, such as allow_url_include, and ensure open_basedir restrictions are enforced.
  • Monitor web server logs for anomalous requests containing path traversal sequences or unusual file parameter values targeting the plugin.
  • Conduct a review of any WordPress installations using the Vavo theme/Vavo Core plugin to confirm current version and exposure.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge