CVE-2025-52998

CRITICALNVD 9.89.8
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: nvd
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

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

Chamilo is a learning management system. Prior to version 1.11.30, in the application, deserialization of data is performed, the data can be spoofed. An attacker can create objects of arbitrary classes, as well as fully control their properties, and thus modify the logic of the web application's operation. This issue has been patched in version 1.11.30.

CVSS v3
9.8
EG Score
9.8(low)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

March 2, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

PHAR deserialization bypass (<=1.11.28) · Advisory · chamilo/chamilo-lms · GitHub

https://github.com/chamilo/chamilo-lms/security/advisories/GHSA-6mwg-2mw5-rx5v
github_release Patch Available

v1.11.30

Patch available: chamilo/chamilo-lms v1.11.30

https://github.com/chamilo/chamilo-lms/releases/tag/v1.11.30
github_commit

commit ba7e15d8cfef (chamilo/chamilo-lms)

Fix landed in chamilo/chamilo-lms commit ba7e15d8cfef — awaiting tagged release

https://github.com/chamilo/chamilo-lms/commit/ba7e15d8cfefcd451de939e98d461b17e72eb627

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 3× in last 7d / 3× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-28 15:35 UTCEPSS rescore
  2. 2026-07-27 13:59 UTCEG score recompute
  3. 2026-07-27 13:57 UTCOSV refresh

Frequently asked(5)

What is CVE-2025-52998?
CVE-2025-52998 is a critical vulnerability published on March 2, 2026. Chamilo is a learning management system. Prior to version 1.11.30, in the application, deserialization of data is performed, the data can be spoofed. An attacker can create objects of arbitrary classes, as well as fully control their properties, and thus modify the logic of the web application's…
When was CVE-2025-52998 disclosed?
CVE-2025-52998 was first published in the National Vulnerability Database on March 2, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-52998 actively exploited?
CVE-2025-52998 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.7% of all scored CVEs.
What is the CVSS score of CVE-2025-52998?
CVE-2025-52998 has a CVSS v3 base score of 9.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2025-52998?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-52998, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-52998

Explore →

Is Your Infrastructure Affected by CVE-2025-52998?

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