CVE-2021-32099 in the critical feed json
A SQL injection vulnerability in the pandora_console component of Artica Pandora FMS 742 allows an unauthenticated attacker to upgrade his…
published 5y ago modified 4mo ago also EUVD-2021-18958
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 12.7%
- EPSS 12.7% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
A SQL injection vulnerability in the pandora_console component of Artica Pandora FMS 742 allows an unauthenticated attacker to upgrade his unprivileged session via the /include/chart_generator.php session_id parameter, leading to a login bypass.
Is CVE-2021-32099 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
12.71% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- blog.sonarsource.com https://blog.sonarsource.com/pandora-fms-742-critical-code-vulnerabilities-explained referenced PoC, tagged "exploit" by a source, unverified
- portswigger.net https://portswigger.net/daily-swig/multiple-vulnerabilities-in-pandora-fms-could-trigger-remote-execution-attack referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
blog.sonarsource.com
/pandora-fms-742-critical-code-vulnerabilities-explained
exploit, third-party-advisory
-
portswigger.net
/daily-swig/multiple-vulnerabilities-in-pandora-fms-could-trigger-remote-execution-attack
exploit, third-party-advisory
-
pandorafms.com
/blog/whats-new-in-pandora-fms-743/
release-notes, vendor-advisory
Sources
- CVE List CVE-2021-32099
- NVD CVE-2021-32099
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.