Authenticated code execution via backup XML handler injection
Published Sep 28, 2022 · Updated May 21, 2025
Code injection in TP-Link Archer AX10 V1 firmware 1.3.1 Build 20220401 allows remote authenticated users to execute arbitrary code. The restore path imports modified backup XML whose renamed button node bypasses protection for a handler parameter and installs an attacker-chosen command. Administrative web-interface access and a configuration restore are required; triggering the injected handler opens a shell on the router.
Summary
What happened
Code injection in TP-Link Archer AX10 V1 firmware 1.3.1 Build 20220401 allows remote authenticated users to execute arbitrary code. The restore path imports modified backup XML whose renamed button node bypasses protection for a handler parameter and installs an attacker-chosen command. Administrative web-interface access and a configuration restore are required; triggering the injected handler opens a shell on the router.
The record
- CVE
- CVE-2022-40486
- Published
- Sep 28, 2022
- Updated
- May 21, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94, T1059.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 28, 2022CVE publishedPublication date reported by the CVE source.
- May 21, 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
- TP-Link Archer AX10 V1 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