File read and code execution via LFI
Published Aug 18, 2026 · Updated Aug 18, 2026
Local file inclusion in Vavo Core 2.3.0 and earlier allows remote attackers to read server files via unspecified vectors. Public records do not identify the vulnerable endpoint, parameter, or function; the flaw is only described as unsafe inclusion of attacker-influenced local path input. No authentication is required, and code execution depends on the presence of attacker-reachable executable local files rather than on file inclusion alone.
Summary
What happened
Local file inclusion in Vavo Core 2.3.0 and earlier allows remote attackers to read server files via unspecified vectors. Public records do not identify the vulnerable endpoint, parameter, or function; the flaw is only described as unsafe inclusion of attacker-influenced local path input. No authentication is required, and code execution depends on the presence of attacker-reachable executable local files rather than on file inclusion alone.
The record
- CVE
- CVE-2026-28570
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- Spab Rice
- Product
- Vavo Core
- Classifications
- CWE-98, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=2.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo