Script execution via transactional-map name injection
Published Aug 5, 2022 · Updated Jun 2, 2026
Cross-site scripting in Pandora FMS 756 and earlier allows attackers to execute JavaScript through a crafted transactional-map name. The console fails to neutralize the name value before placing it in a generated page, so the browser interprets injected script as code. Exploitation requires creation or editing of a transactional map and a user to render the affected name; successful execution occurs in that viewer's browser context.
Summary
What happened
Cross-site scripting in Pandora FMS 756 and earlier allows attackers to execute JavaScript through a crafted transactional-map name. The console fails to neutralize the name value before placing it in a generated page, so the browser interprets injected script as code. Exploitation requires creation or editing of a transactional map and a user to render the affected name; successful execution occurs in that viewer's browser context.
The record
- CVE
- CVE-2021-46676
- Published
- Aug 5, 2022
- Updated
- Jun 2, 2026
- Vendor
- Pandora FMS
- Product
- Pandora FMS
- Classifications
- CWE-79, CAPEC-63, T1059.007
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 5, 2022CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record 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=v756 <=v756
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.
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