CVE-2023-24518
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 · uneditedA Cross-site Request Forgery (CSRF) vulnerability in Pandora FMS allows an attacker to force authenticated users to send a request to a web application they are currently authenticated against. This issue affects Pandora FMS version 767 and earlier 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 · moderate confidenceCSRF vulnerability in Pandora FMS allows attackers to trick authenticated users into unknowingly submitting malicious requests. Since the user's session cookies are automatically sent with requests, attackers can exploit the lack of anti-CSRF token validation to perform unauthorized actions on behalf of logged-in users.
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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L
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 via the admin console, version file, or package manager. This is typically visible in the footer of the web interface or stored in a version configuration file within the installation directory.Affected if The installed version is 767 or any version lower than 767.
-
Verify anti-CSRF token presence in formsLog into Pandora FMS as a regular user and inspect the HTML source of state-changing forms (such as user management, configuration changes, or data submission forms). Look for a hidden input field containing a CSRF token value, or check if the form submission includes a token parameter.Affected if State-changing forms lack anti-CSRF token parameters in the request payload.
-
Test token validation on form submissionSubmit a legitimate state-changing form request while capturing the request in a proxy. Then replay that same request without the token parameter to see if the action is still processed by the server.Affected if Requests without a valid anti-CSRF token are accepted and the action is executed successfully.
-
Check session cookie SameSite attributeInspect the session cookie configuration in the browser developer tools under the Application/Storage tab, or examine the Set-Cookie headers in HTTP responses from the server.Affected if The session cookie lacks a SameSite attribute or is set to None without Secure flag, making cross-origin requests possible.
Your environment is affected if the installed Pandora FMS version is 767 or lower and state-changing operations do not require valid anti-CSRF tokens.
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 vendor patch or upgrade to a version newer than 767. As an interim measure, configure a WAF to validate Origin/Referer headers and reject requests without proper anti-CSRF tokens.
- Consultation2.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,400.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24518 — 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-24518 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