Administrative file read via undisclosed template action
Published Feb 1, 2023 · Updated Mar 27, 2025
Arbitrary file read in LMXCMS 1.41 allows remote authenticated users with administrative privileges to read server files. The public record identifies TemplateAction.class.php but does not disclose the request parameter, file operation, or missing validation that enables the read. Administrative access is required, and the reported consequence is file disclosure without modification or service interruption.
Summary
What happened
Arbitrary file read in LMXCMS 1.41 allows remote authenticated users with administrative privileges to read server files. The public record identifies TemplateAction.class.php but does not disclose the request parameter, file operation, or missing validation that enables the read. Administrative access is required, and the reported consequence is file disclosure without modification or service interruption.
The record
- CVE
- CVE-2022-48094
- Published
- Feb 1, 2023
- Updated
- Mar 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-552, T1005
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Feb 1, 2023CVE publishedPublication date reported by the CVE source.
- Mar 27, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Yuque arbitrary file-read proof of conceptproof of concept · unverified
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