CVE-2017-15936
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Artica Pandora FMS version 7.0, an Attacker with write Permission can create an agent with an XSS Payload; when a user enters the agent definitions page, the script will get executed.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceArtica Pandora FMS 7.0 contains a stored Cross-Site Scripting (XSS) vulnerability where an authenticated attacker with write permissions can embed malicious JavaScript into an agent's definition. When legitimate users access the agent definitions page, the embedded payload executes in their browser session, potentially enabling session hijacking, credential theft, or further propagation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Pandora FMS versionAccess the Pandora FMS console and navigate to the admin or about page, or check the version via the built-in 'About' option typically found in the system administration section. If direct access is unavailable, check the installation directory for version files or examine the HTTP server banner.Affected if The installed version is exactly 7.0 (or falls within the 7.0 release line) since only version 7.0 is listed as affected.
-
Confirm access to the Pandora FMS web interfaceAttempt to log in to the Pandora FMS web console using valid credentials. Verify the main dashboard loads successfully.Affected if The application is accessible and operational, which is required for the XSS to be triggered.
-
Verify the presence of agent definitionsNavigate to the agent management or monitoring section of the console where agent definitions are listed. Look for any configured agents in the system.Affected if There are agent definitions present in the system, as the XSS payload would be embedded within an agent's definition fields.
-
Check for users with write permissionsAccess the user management or access control section of the admin panel. Review user roles and permissions to identify accounts that have write or create permissions for agents.Affected if There exist users with write permissions to agent definitions, as this is a prerequisite for an attacker to embed the malicious payload.
-
Inspect agent definition input fields for unsanitized outputCreate a new agent or edit an existing one. In the agent name or description fields, input a test string containing HTML or script tags such as <script>alert('test')</script>. Save the agent definition, then navigate to the agent definitions list page to observe whether the script executes or the raw tags render.Affected if The injected script tags execute or the HTML renders unescaped when viewing the agent definitions page, indicating the XSS vulnerability is present and exploitable.
A user is affected if they are running Pandora FMS version 7.0 with the web interface accessible and agents defined, where agent definition fields accept and render unsanitized input, allowing stored XSS to execute when the agent definitions page is viewed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement robust input validation and output encoding for all agent-related fields, particularly during agent creation and when rendering the agent definitions page. Additionally, deploy Content Security Policy (CSP) headers to mitigate XSS execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15936 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-15936 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data