dbcve.org
Pandora FmsApplication · Pandorafms

CVE-2023-41814

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-29
Fix available
A fix is available. Upgrade to after 774 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Pandora FMS on all allows Cross-Site Scripting (XSS). Through an HTML payload (iframe tag) it is possible to carry out XSS attacks when the user receiving the messages opens their notifications. This issue affects Pandora FMS: from 700 through 774.

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 confidence

Stored XSS vulnerability in Pandora FMS notification system where improper input validation allows iframe tags to be injected via notifications. When users view their notifications, the malicious HTML/iframe payload executes, enabling attacker-controlled script execution in victim browsers.

MitigationImplement proper output encoding/sanitization on all notification display paths and add input validation on notification creation. Consider Content-Security-Policy headers to mitigate XSS impact.

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
Pandora FmsApplication
Affected:>= 700, <= 774

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Pandora FMS version
    Access the Pandora FMS console administration panel or run: grep -r 'define.*VERSION' /path/to/pandora_console/include 2>/dev/null. Also check /pandora_console/CHANGELOG or version.txt if accessible.
    Affected if Installed version is >= 700 and <= 774 (v7.0 to v7.74)
  2. Verify notification module is accessible
    Log into Pandora FMS as a standard user and navigate to the notifications section (typically at /pandora_console/index.php?sec=workspace&sec2=operation/users/visualizacion'). Confirm the notification bell/panel loads.
    Affected if Notification feature is enabled and user-accessible in the environment
  3. Inspect stored notification data for injected payloads
    Query the database for suspicious iframe/script tags. Run: mysql -u pandora -p pandora -e "SELECT id_notification, id_user, subject, message FROM tnotification WHERE message LIKE '%<iframe%' OR message LIKE '%<script%' OR message LIKE '%javascript:%';"
    Affected if Any notifications contain unencoded iframe, script, or javascript: URL patterns
  4. Check notification creation endpoints for input sanitization
    Review PHP files handling notification creation: look for /pandora_console/ajax/*notification*.php or similar. Search for absence of htmlspecialchars, strip_tags, or sanitization functions around the notification message field.
    Affected if Code lacks output encoding on notification message fields before storage or display
  5. Review recent notification creation logs
    Check Pandora FMS event logs and access logs for POST requests to notification creation endpoints containing patterns like 'iframe', 'script', or 'onload'. Look in /var/log/apache2/error.log or similar web server logs.
    Affected if Recent notification creation attempts contain suspicious HTML/iframe payload patterns

Environment is affected if Pandora FMS version is between 700 and 774 AND the notification module is accessible with unvalidated input handling allowing injected iframe/script tags in stored notifications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 774
Interim mitigation

Implement proper output encoding/sanitization on all notification display paths and add input validation on notification creation. Consider Content-Security-Policy headers to mitigate XSS impact.

Fix this in Pandora Fms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-41814 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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