CVE-2021-46676: Vulnerability XSS in Transaction Map name field
A XSS vulnerability exist in Pandora FMS version 756 and below, that allows an attacker to perform javascript code executions via the transactional maps name field.
Security readout for executives and security teams
Plain-English summary
CVE-2021-46676 is a cross-site scripting issue in Pandora FMS where a Transactional Maps name can trigger JavaScript execution. The published score is medium, but impact depends on who can edit that field and who views it.
Executive priority
Treat as a controlled but real application-security issue. Prioritize remediation where Pandora FMS is internet-accessible, broadly administered, or used by security operations teams.
Technical view
The issue is CWE-79 XSS in Pandora FMS 756 and earlier, tied to the Transactional Maps name field. CVSS 3.1 is 4.0 with local attack vector, low complexity, high privileges required, and user interaction required.
Likely exposure
Exposure is most likely in organizations running Pandora FMS version 756 or earlier with privileged users able to create or edit Transactional Maps.
Exploitation context
The bundle does not cite active exploitation, and it is not listed as CISA KEV. Exploitation appears constrained by high privileges and required user interaction.
Researcher notes
Evidence is limited to the CVE description, CVSS vector, CWE-79 classification, and vendor/INCIBE references. No exploit status, fixed version, or workaround is provided in the supplied bundle.
Mitigation direction
Check Pandora FMS vendor guidance for the fixed release or supported remediation.
Inventory Pandora FMS deployments and flag versions 756 or earlier.
Restrict Transactional Maps editing to trusted administrators until remediated.
Review access controls for privileged Pandora FMS accounts.
Validation and detection
Confirm the installed Pandora FMS version on each deployment.
Identify users or roles that can edit Transactional Maps names.
Review recent Transactional Maps changes for unexpected or suspicious names.
Check vendor advisories before closing remediation work.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.