Authenticated PHP execution via local file inclusion
Published Jun 2, 2026 · Updated Jun 2, 2026
Local file inclusion in UnboundStudio Accordion FAQ 2.2.1 and earlier allows remote authenticated users to execute local PHP files. Published records do not name the vulnerable function or request parameter; they establish that attacker-controlled input reaches a PHP include operation. Contributor-level WordPress access and an includable local PHP file are required, while successful exploitation grants code execution in the web server context.
Summary
What happened
Local file inclusion in UnboundStudio Accordion FAQ 2.2.1 and earlier allows remote authenticated users to execute local PHP files. Published records do not name the vulnerable function or request parameter; they establish that attacker-controlled input reaches a PHP include operation. Contributor-level WordPress access and an includable local PHP file are required, while successful exploitation grants code execution in the web server context.
The record
- CVE
- CVE-2025-58024
- Published
- Jun 2, 2026
- Updated
- Jun 2, 2026
- Vendor
- UnboundStudio
- Product
- Accordion FAQ
- Classifications
- CWE-98, CAPEC-252, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 2, 2026CVE publishedPublication date reported by the CVE source.
- Jun 2, 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.2.1
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