Configuration modification via unauthenticated file upload
Published Apr 17, 2024 · Updated Nov 4, 2025
Improper access control in Peplink Smart Reader 1.2.0 allows remote attackers to stage configuration changes through an HTTP upload. The upload_config.cgi handler performs no authentication, decodes and minimally validates the supplied archive, then copies it into /etc/masterconfig. An authenticated user must apply the staged changes; doing so can replace the administrative password, cause lockout, and grant the attacker future authenticated access.
Summary
What happened
Improper access control in Peplink Smart Reader 1.2.0 allows remote attackers to stage configuration changes through an HTTP upload. The upload_config.cgi handler performs no authentication, decodes and minimally validates the supplied archive, then copies it into /etc/masterconfig. An authenticated user must apply the staged changes; doing so can replace the administrative password, cause lockout, and grant the attacker future authenticated access.
The record
- CVE
- CVE-2023-45744
- Published
- Apr 17, 2024
- Updated
- Nov 4, 2025
- Vendor
- Peplink
- Product
- Smart Reader
- Classifications
- CWE-284, T1098
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=v1.2.0
- Affected versionversion=v1.2.0 (in QEMU)
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.
Public exploit references
- Talos configuration-upload proof of conceptproof of concept · demonstrated
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