dbcve.org
Pandora FmsApplication · Artica

CVE-2023-41811

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-23
Fix available
A fix is available. Upgrade to after 773 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). This vulnerability allowed Javascript code to be executed in the news section of the web console. This issue affects Pandora FMS: from 700 through 773.

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 · moderate confidence

A stored Cross-Site Scripting (XSS) vulnerability in Pandora FMS versions 700-773 allows attackers to inject malicious JavaScript code into the news section of the web console. When authenticated users view the compromised news content, the injected script executes in their browser session, potentially leading to session hijacking or credential theft.

MitigationImplement proper input validation and output encoding for all user-supplied content in the news section. Consider adding Content-Security-Policy headers to restrict script execution. Upgrade to version 774 or later which contains the security fix.

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, <= 773

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 Pandora FMS installed version
    Locate the version file or check the web console footer/login page for the version number. Common locations include the installer directory or the about section in the admin panel.
    Affected if The installed version falls within the range 700 to 773 inclusive.
  2. Confirm web console access
    Navigate to the Pandora FMS web interface and verify the console is accessible. Try reaching the main login page and confirming the URL matches your deployment.
    Affected if The web console is reachable and serves content from a version in the affected range.
  3. Verify news module is present
    Log into the web console and locate the news section, typically found in the main dashboard, sidebar menu under 'Events' or 'News', or a dedicated news widget area.
    Affected if The news module or news widget is visible and functional in the web interface.
  4. Inspect existing news entries
    Access the news section in the console and review all published news items. Look for any entries containing unusual script tags, javascript: URLs, event handlers (onclick, onload, onerror), or encoded characters that may indicate injected payloads.
    Affected if Any news entry contains suspicious JavaScript code, script tags, or encoded payloads that were not created by authorized administrators.

You are affected if your Pandora FMS installation is version 700 through 773, the web console is accessible, and the news section contains unexpected or malicious-looking content with script injection payloads.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 773
Interim mitigation

Implement proper input validation and output encoding for all user-supplied content in the news section. Consider adding Content-Security-Policy headers to restrict script execution. Upgrade to version 774 or later which contains the security fix.

Recommended fix Moderate confidence

latest stable release (version 774 or higher, or 8.0+ if available)

  1. 1. Identify your current Pandora FMS version in the web console (typically found in the footer or in the administration section)
  2. 2. Before upgrading, perform a full backup of your Pandora FMS database and configuration files
  3. 3. Download the latest stable Pandora FMS version from the official repository at pandorafms.com
  4. 4. Follow the official upgrade documentation for your specific deployment method (package-based or source-based installation)
  5. 5. After upgrade, verify the news section functionality and confirm the XSS vulnerability is resolved by testing that JavaScript code is no longer executable in news entries
  6. 6. Review user permissions and consider implementing additional input validation for the news module
Caveat Review release notes for version-specific changes; major version upgrades (e.g., 7.x to 8.x) may require configuration migration and have potential breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pandora Fms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41811 — 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-41811 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