Script execution through website name injection
Published Jan 18, 2024 · Updated Jun 5, 2025
Cross-site scripting in FlyCms 1.0 allows remote authenticated users to execute injected script through the website-name setting. The record identifies the website-name field as the injection locus but does not disclose the handler, storage path, or missing output-encoding operation. Exploitation requires low-privileged network access and victim interaction; the script executes in the FlyCms origin and can read or alter browser-accessible data.
Summary
What happened
Cross-site scripting in FlyCms 1.0 allows remote authenticated users to execute injected script through the website-name setting. The record identifies the website-name field as the injection locus but does not disclose the handler, storage path, or missing output-encoding operation. Exploitation requires low-privileged network access and victim interaction; the script executes in the FlyCms origin and can read or alter browser-accessible data.
The record
- CVE
- CVE-2024-22548
- Published
- Jan 18, 2024
- Updated
- Jun 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 18, 2024CVE publishedPublication date reported by the CVE source.
- Jun 5, 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
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