Script execution via permission management output
Published Jan 1, 2024 · Updated Jun 3, 2025
Cross-site scripting in FlyCms through abbaa5a allows remote attackers to execute script via the permission management feature. The public proof of concept supplies an HTML image event-handler payload, but it does not identify the accepting parameter or rendering path. Execution requires a user to render the affected output, exposing data and actions available to that browser session.
Summary
What happened
Cross-site scripting in FlyCms through abbaa5a allows remote attackers to execute script via the permission management feature. The public proof of concept supplies an HTML image event-handler payload, but it does not identify the accepting parameter or rendering path. Execution requires a user to render the affected output, exposing data and actions available to that browser session.
The record
- CVE
- CVE-2024-21732
- Published
- Jan 1, 2024
- Updated
- Jun 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 1, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 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
- FlyCms permission-management XSS 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