Unauthenticated local file disclosure via filename control
Published Jan 22, 2026 · Updated Jan 22, 2026
Local file inclusion in TangibleWP Listivo Core 2.3.77 and earlier allows remote attackers to expose local file contents without authentication. Patchstack has not published the vulnerable endpoint, parameter, or include/require call, so the precise filename-control failure is undisclosed. A crafted network request can select a local file and display its output, with consequences bounded by files readable to the WordPress PHP process.
Summary
What happened
Local file inclusion in TangibleWP Listivo Core 2.3.77 and earlier allows remote attackers to expose local file contents without authentication. Patchstack has not published the vulnerable endpoint, parameter, or include/require call, so the precise filename-control failure is undisclosed. A crafted network request can select a local file and display its output, with consequences bounded by files readable to the WordPress PHP process.
The record
- CVE
- CVE-2025-67957
- Published
- Jan 22, 2026
- Updated
- Jan 22, 2026
- Vendor
- TangibleWP
- Product
- Listivo Core
- Classifications
- CWE-98, CAPEC-252, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 2026CVE publishedPublication date reported by the CVE source.
- Jan 22, 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.77 changes=[{"at":"2.3.78","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