dbcve.org
Pandora FmsApplication · Artica

CVE-2026-30807

HIGH · 8.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 777.17 / 802 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery vulnerability allows an attacker to perform unauthorized actions via crafted web page. This issue affects Pandora FMS: from 777 through 800

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

Cross-Site Request Forgery (CSRF) vulnerability in Pandora FMS allows an attacker to trick authenticated users into performing unintended actions (such as adding admin users, modifying settings, or deleting data) by embedding malicious requests in crafted web pages. The vulnerability exists due to missing or inadequate anti-CSRF token validation in the application's forms and state-changing endpoints.

MitigationImplement synchronizer token pattern by adding unique anti-CSRF tokens to all state-changing forms and validating these tokens server-side on every POST request. Additionally, configure SameSite attribute for session cookies and validate Origin/Referer headers as defense-in-depth measures.

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:< 777.17>= 778, < 802

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Determine installed Pandora FMS version
    Access the Pandora FMS web interface and navigate to Administration > Setup > About, or check the version file in the installation directory (typically /var/www/html/pandora_console/include/config.php or similar). Compare the version number to the affected ranges: < 777.17 or >= 778, < 802.
    Affected if The installed version falls within < 777.17 or >= 778 and < 802.
  2. Inspect login form for anti-CSRF token
    Log into Pandora FMS and view the HTML source of any state-changing form (e.g., user creation, system settings, or configuration changes). Search for a hidden input field containing a token value (commonly named 'token', 'csrf_token', 'anticsrf', or similar).
    Affected if No anti-CSRF token field is present in the form HTML.
  3. Verify token is submitted and validated
    Submit a state-changing form request and inspect the server response or HTTP headers to confirm the token is being validated server-side. Alternatively, attempt a request without the token to see if it is accepted.
    Affected if The application accepts requests without a valid anti-CSRF token or the token parameter is not validated server-side.
  4. Check session cookie SameSite attribute
    Log into Pandora FMS and inspect session cookies using browser developer tools (Application > Cookies) or via curl. Verify if the session cookie has the SameSite attribute set to 'Strict' or 'Lax'.
    Affected if The session cookie lacks a SameSite attribute or is set to 'None' without Secure flag.

You are affected if your Pandora FMS version is below 777.17 or between 778 and 802, AND the application lacks proper anti-CSRF token validation on state-changing forms.

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 777.17 / 802 or later
Fixed in 777.17802
Interim mitigation

Implement synchronizer token pattern by adding unique anti-CSRF tokens to all state-changing forms and validating these tokens server-side on every POST request. Additionally, configure SameSite attribute for session cookies and validate Origin/Referer headers as defense-in-depth measures.

Recommended fix Moderate confidence

Pandora FMS 802 or later stable release

  1. 1. Identify the current Pandora FMS version by checking the system info or looking at the version file (typically in /var/www/html/pandora_console/include/config.php or similar)
  2. 2. Review the Pandora FMS 802 release notes for any specific upgrade requirements or breaking changes
  3. 3. Create a full backup of the Pandora FMS database and configuration files before upgrading
  4. 4. Download Pandora FMS version 802 or later from the official source (pandorafms.com)
  5. 5. Follow the official upgrade procedure for your installation method (online repository upgrade or manual package installation)
  6. 6. After upgrade, verify the new version is running (should show version 802 or higher)
  7. 7. Test that CSRF protections are functioning by attempting normal operations in the web interface
Caveat Review 802 release notes - some database schema changes or configuration adjustments may be required during upgrade

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

Fix this in Pandora Fms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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