CVE-2023-0828
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 · uneditedCross-site Scripting (XSS) vulnerability in Syslog Section of Pandora FMS allows attacker to cause that users cookie value will be transferred to the attackers users server. This issue affects Pandora FMS v767 version and prior versions on all platforms.
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 confidenceStored XSS vulnerability in the Syslog section of Pandora FMS allows attackers to inject malicious scripts that can exfiltrate user session cookies to an attacker-controlled server. This affects version 767 and prior versions across all platforms.
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<= 767CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 Pandora FMS versionLocate the installed Pandora FMS version number in the system (typically found in the web interface footer, about page, or via command-line tools provided by the installation)Affected if The installed version is 767 or any version lower than 767 (all versions up to and including 767 are affected)
-
Verify Syslog module is enabledConfirm that the Syslog feature or module is enabled and accessible within the Pandora FMS installationAffected if The Syslog module is active in the environment, as this is the affected component where the vulnerability exists
-
Check access to Syslog sectionDetermine if any user accounts have access to view or interact with the Syslog section of the web interfaceAffected if Users can access the Syslog section, as this is the attack surface where malicious scripts can be injected
-
Inspect Syslog entries for script tagsReview the Syslog display/output in the web interface for any unexpected HTML or JavaScript content, particularly script tags, iframe elements, or event handlers (onclick, onerror, etc.)Affected if Unexpected script tags or JavaScript code appear in the Syslog entries, indicating potential exploitation or injection
-
Review session cookie configurationExamine the session cookie settings for the Pandora FMS web application (check browser developer tools or server configuration for HttpOnly and Secure flags)Affected if Session cookies lack HttpOnly or Secure flags, making them vulnerable to exfiltration by injected scripts
The environment is affected if Pandora FMS version 767 or lower is installed AND the Syslog section is accessible to users.
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 dataApply input validation and output encoding to all user-supplied data displayed in the Syslog section, and configure session cookies with HttpOnly and Secure flags to prevent cookie exfiltration.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0828 — 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-2023-0828 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