Browser script execution via stored extension name
Published Jul 25, 2021 · Updated Aug 4, 2024
Stored cross-site scripting in NCH Axon PBX 2.22 and earlier allows remote authenticated users to run scripts via an extension name. The web control panel stores an extension-name payload without adequate input validation and later renders it as executable browser content. An authenticated account and later browser rendering of the saved extension are required; the code runs in the viewing user's Axon origin.
Summary
What happened
Stored cross-site scripting in NCH Axon PBX 2.22 and earlier allows remote authenticated users to run scripts via an extension name. The web control panel stores an extension-name payload without adequate input validation and later renders it as executable browser content. An authenticated account and later browser rendering of the saved extension are required; the code runs in the viewing user's Axon origin.
The record
- CVE
- CVE-2021-37453
- Published
- Jul 25, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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
- Axon PBX 2.22 stored XSS 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