Arbitrary file read via unsafe include path
Published Aug 20, 2026 · Updated Aug 20, 2026
Local file inclusion in Uxper Golo Framework before 1.7.5 allows remote attackers to read local files via crafted web requests. Public records do not name the exact PHP function, but the CNA maps the flaw to CWE-98 and Uxper's 1.7.5 changelog says file-include validation was strengthened and an LFI in the Elementor Blog Widget was fixed, indicating a user-influenced template path reached a PHP include or require operation without sufficient validation. No authentication or user interaction is required; exposure depends on the vulnerable widget or endpoint being reachable, and the documented impact is file disclosure, with Patchstack noting that credential files can enable broader compromise in some deployments.
Summary
What happened
Local file inclusion in Uxper Golo Framework before 1.7.5 allows remote attackers to read local files via crafted web requests. Public records do not name the exact PHP function, but the CNA maps the flaw to CWE-98 and Uxper's 1.7.5 changelog says file-include validation was strengthened and an LFI in the Elementor Blog Widget was fixed, indicating a user-influenced template path reached a PHP include or require operation without sufficient validation. No authentication or user interaction is required; exposure depends on the vulnerable widget or endpoint being reachable, and the documented impact is file disclosure, with Patchstack noting that credential files can enable broader compromise in some deployments.
The record
- CVE
- CVE-2026-28150
- Published
- Aug 20, 2026
- Updated
- Aug 20, 2026
- Vendor
- Uxper
- Product
- Golo Framework
- Classifications
- CWE-98, CAPEC-252, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 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 <1.7.5 changes=[{"at":"1.7.5","status":"unaffected"}]
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