Unauthenticated local file inclusion via SDK proxy
Published Dec 18, 2024 · Updated May 11, 2026
A local file inclusion flaw in Axeptio for WordPress 2.5.4 and earlier allows remote attackers to read server files through the SDK proxy. The public record places the flaw in SDK proxy file handling but does not disclose the endpoint, parameter, or exact include operation. No authentication is required; exposed readable files can disclose server data, including credentials stored in configuration files.
Summary
What happened
A local file inclusion flaw in Axeptio for WordPress 2.5.4 and earlier allows remote attackers to read server files through the SDK proxy. The public record places the flaw in SDK proxy file handling but does not disclose the endpoint, parameter, or exact include operation. No authentication is required; exposed readable files can disclose server data, including credentials stored in configuration files.
The record
- CVE
- CVE-2024-54270
- Published
- Dec 18, 2024
- Updated
- May 11, 2026
- Vendor
- Axeptio
- Product
- Axeptio
- Classifications
- CWE-98, CAPEC-252, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 18, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=0 <=2.5.4 changes=[{"at":"2.5.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