dbcve.org
Pandora FmsApplication · Artica

CVE-2026-30810

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 →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Server-Side Request Forgery vulnerability allows Privilege Escalation via API Checker extension. 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 · moderate confidence

Server-Side Request Forgery (SSRF) vulnerability in the API Checker extension of Pandora FMS versions 777-800 allows attackers to make the server perform arbitrary requests to internal or external resources, potentially leading to privilege escalation through access to internal services or administrative interfaces.

MitigationRestrict the API Checker to validate and allowlist permitted target URLs/hosts, implement strict input sanitization, and enforce network segmentation to prevent internal service access from the application server.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Identify Pandora FMS version
    Locate the Pandora FMS installation and determine the installed version number. This is typically visible in the login page footer, in the 'About' section of the admin panel, or by querying the system package manager if installed via OS packages.
    Affected if The installed version is 777 through 800 inclusive, or specifically less than 777.17 when in the 777.x line.
  2. Confirm API Checker extension presence
    Navigate to the Pandora FMS admin console and check whether the 'API Checker' extension is installed and enabled. This is typically found under the 'Extensions' or 'Admin Tools' menu sections.
    Affected if The API Checker extension is installed and enabled in the Pandora FMS environment.
  3. Review extension configuration
    Access the API Checker extension settings page and examine its configuration for any user-defined URLs, endpoints, or request parameters that could be controlled by authenticated users.
    Affected if The API Checker allows user-supplied URLs or endpoints to be specified in requests without validation.
  4. Inspect server access logs
    Review Pandora FMS and web server access logs for requests to the API Checker endpoint that show unusual or unexpected destination URLs, particularly internal network addresses (such as 127.0.0.1, 10.x.x.x, 192.168.x.x) or cloud metadata endpoints.
    Affected if Logs show requests from the API Checker making calls to internal resources or unexpected external domains.

A user is affected if they are running Pandora FMS versions 777 through 800 with the API Checker extension enabled, as this combination allows authenticated users to trigger arbitrary server-side requests.

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

Restrict the API Checker to validate and allowlist permitted target URLs/hosts, implement strict input sanitization, and enforce network segmentation to prevent internal service access from the application server.

Recommended fix Moderate confidence

Pandora FMS 777.17 or 802+ (depending on your current branch)

  1. 1. Backup your current Pandora FMS installation and database before proceeding with any upgrade.
  2. 2. Download the latest stable version of Pandora FMS from the official repository or pandorafms.com.
  3. 3. If running version 777.x, upgrade to version 777.17 or later.
  4. 4. If running version 778.x through 801.x, upgrade to version 802 or later.
  5. 5. Verify the API Checker extension is updated and functioning correctly after upgrade.
  6. 6. Test that the SSRF vulnerability is no longer exploitable by attempting unauthorized API requests.
Caveat Review release notes for version 777.17 and 802+ for any configuration or feature changes that may affect your deployment

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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