CVE-2014-125124

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 2.3% (83rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekWeaponized
10.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit code is available (Metasploit)
CISA-KEV: Not listedEPSS PROB: 2.3%CVSS: 10.0Exploit: MetasploitExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists Artica ST Pandora FMS versions up to and including 5.0RC1 as affected. No release containing a fix is confirmed on record.

An unauthenticated remote command execution vulnerability exists in Pandora FMS versions up to and including 5.0RC1 via the Anyterm web interface, which listens on TCP port 8023. The anyterm-module endpoint accepts unsanitized user input via the p parameter and directly injects it into a shell command, allowing arbitrary command execution as the pandora user. In certain versions (notably 4.1 and 5.0RC1), the pandora user can elevate privileges to root without a password using a chain involving the artica user account. This account is typically installed without a password and is configured to run sudo without authentication. Therefore, full system compromise is possible without any credentials.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
86
EG Risk 86/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
2.3%
EPSS %ILE
83rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
2.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 31, 2025

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated Oct 17, 2026
No fix on record yet.
Web page

Pandora FMS <= 5.0RC1 Anyterm Unauthenticated Command Injection | Advisories | VulnCheck

https://www.vulncheck.com/advisories/pandora-fms-anyterm-unauth-command-injection
Web page

Pandora Fms - Remote Code Execution (Metasploit) - Linux remote Exploit

https://www.exploit-db.com/exploits/31518
Web page
https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/linux/http/pandora_fms_exec.rb

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 175 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 79 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 05:38 UTCEG score recompute
  2. 2026-10-23 05:38 UTCGHSA enrichmentGHSA-9whg-3jfv-8hgp · GitHub severity CRITICAL
  3. 2026-10-22 16:26 UTCEPSS rescoreEPSS 2.3% · 83rd percentile
  4. 2026-10-22 05:48 UTCEG score recompute
  5. 2026-10-22 05:48 UTCGHSA enrichmentGHSA-9whg-3jfv-8hgp · GitHub severity CRITICAL
  6. 2026-10-21 16:26 UTCEPSS rescoreEPSS 2.3% · 83rd percentile
  7. 2026-10-21 05:56 UTCEG score recompute
  8. 2026-10-21 05:55 UTCGHSA enrichmentGHSA-9whg-3jfv-8hgp · GitHub severity CRITICAL
  9. 2026-10-20 16:26 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  10. 2026-10-20 06:04 UTCEG score recompute
  11. 2026-10-20 06:04 UTCGHSA enrichmentGHSA-9whg-3jfv-8hgp · GitHub severity CRITICAL
  12. 2026-10-19 16:26 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  13. 2026-10-19 06:12 UTCEG score recompute
  14. 2026-10-19 06:12 UTCGHSA enrichmentGHSA-9whg-3jfv-8hgp · GitHub severity CRITICAL
  15. 2026-10-18 16:26 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  16. 2026-10-18 06:21 UTCEG score recompute
  17. 2026-10-18 06:20 UTCGHSA enrichmentGHSA-9whg-3jfv-8hgp · GitHub severity CRITICAL
  18. 2026-10-17 16:26 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  19. 2026-10-17 06:27 UTCEG score recompute
  20. 2026-10-17 06:27 UTCGHSA enrichmentGHSA-9whg-3jfv-8hgp · GitHub severity CRITICAL
  21. 2026-10-16 16:26 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  22. 2026-10-16 06:36 UTCEG score recompute
  23. 2026-10-16 06:36 UTCGHSA enrichmentGHSA-9whg-3jfv-8hgp · GitHub severity CRITICAL
  24. 2026-10-15 16:26 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  25. 2026-10-15 05:16 UTCEG score recompute
Show 71 more
  1. 2026-10-15 05:16 UTCGHSA enrichmentGHSA-9whg-3jfv-8hgp · GitHub severity CRITICAL
  2. 2026-10-14 16:26 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  3. 2026-10-14 00:58 UTCEG score recompute
  4. 2026-10-14 00:58 UTCGHSA enrichmentGHSA-9whg-3jfv-8hgp · GitHub severity CRITICAL
  5. 2026-10-13 16:26 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  6. 2026-10-12 21:04 UTCEG score recompute
  7. 2026-10-12 21:04 UTCGHSA enrichmentGHSA-9whg-3jfv-8hgp · GitHub severity CRITICAL
  8. 2026-10-12 16:27 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  9. 2026-10-12 01:27 UTCEG score recompute
  10. 2026-10-11 13:39 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  11. 2026-10-10 19:54 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  12. 2026-10-09 20:01 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  13. 2026-10-08 16:34 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  14. 2026-10-07 23:39 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  15. 2026-10-06 15:11 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  16. 2026-10-05 17:38 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  17. 2026-10-04 23:16 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  18. 2026-09-30 14:58 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  19. 2026-09-30 00:20 UTCEG score recompute
  20. 2026-09-28 13:45 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  21. 2026-09-27 13:39 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  22. 2026-09-26 15:53 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  23. 2026-09-21 20:25 UTCEPSS rescoreEPSS 2.1% · 80th percentile
  24. 2026-09-20 20:08 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  25. 2026-09-18 19:21 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  26. 2026-09-17 19:21 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  27. 2026-09-15 03:04 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  28. 2026-09-13 16:41 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  29. 2026-09-12 14:55 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  30. 2026-09-11 09:30 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  31. 2026-09-07 15:56 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  32. 2026-09-04 13:55 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  33. 2026-08-30 19:12 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  34. 2026-08-27 14:20 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  35. 2026-08-26 14:41 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  36. 2026-08-25 13:43 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  37. 2026-08-23 00:13 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  38. 2026-08-21 23:44 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  39. 2026-08-20 22:50 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  40. 2026-08-19 16:59 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  41. 2026-08-18 13:43 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  42. 2026-08-16 14:50 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  43. 2026-08-16 02:09 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  44. 2026-08-15 01:25 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  45. 2026-08-09 13:42 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  46. 2026-08-08 16:31 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  47. 2026-08-07 16:21 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  48. 2026-08-06 13:42 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  49. 2026-08-05 19:12 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  50. 2026-08-04 15:04 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  51. 2026-08-01 04:11 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  52. 2026-07-30 16:23 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  53. 2026-07-30 01:26 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  54. 2026-07-28 15:31 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  55. 2026-07-23 14:14 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  56. 2026-07-23 01:12 UTCEG score recompute
  57. 2026-07-23 00:15 UTCEG score recompute
  58. 2026-07-22 21:53 UTCEG score recompute
  59. 2026-07-22 14:04 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  60. 2026-07-21 15:21 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  61. 2026-07-20 17:03 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  62. 2026-07-19 14:27 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  63. 2026-07-19 02:25 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  64. 2026-07-18 10:00 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  65. 2026-07-16 16:58 UTCEPSS rescoreEPSS 1.5% · 70th percentile
  66. 2026-07-15 16:54 UTCEPSS rescoreEPSS 1.5% · 70th percentile
  67. 2026-07-15 01:56 UTCEPSS rescoreEPSS 1.5% · 70th percentile
  68. 2026-07-13 22:26 UTCEPSS rescoreEPSS 1.5% · 70th percentile
  69. 2026-07-13 06:08 UTCEPSS rescoreEPSS 1.5% · 70th percentile
  70. 2026-07-12 05:42 UTCEPSS rescoreEPSS 1.5% · 70th percentile
  71. 2026-07-09 19:05 UTCEPSS rescoreEPSS 1.5% · 70th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Metasploit module). No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • Metasploitexploit/linux/http/pandora_fms_exec✓ verified
    Published Feb 6, 2014

    Pandora FMS Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2014-125124?
CVE-2014-125124 is a critical-severity vulnerability; its CVE record was published on July 31, 2025. An unauthenticated remote command execution vulnerability exists in Pandora FMS versions up to and including 5.0RC1 via the Anyterm web interface, which listens on TCP port 8023. The anyterm-module endpoint accepts unsanitized user input via the p parameter and directly injects it into a shell…
When was CVE-2014-125124 made public?
CVE-2014-125124 was made public on February 7, 2014: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 31, 2025. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2014-125124 actively exploited?
CVE-2014-125124 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 2.3% probability of exploitation in the next 30 days (83rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2014-125124?
CVE-2014-125124 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2014-125124?
No fix for CVE-2014-125124 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's CNA (VulnCheck) lists Artica ST Pandora FMS versions up to and including 5.0RC1 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2014-125124

Explore →

Is Your Infrastructure Affected by CVE-2014-125124?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs