cve.bz

CVE-2026-31941 chamilo chamilo lms: SSRF

6.5 mediumEPSS 0.2%Fix available

Medium (6.5) in chamilo chamilo lms. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Chamilo LMS is a learning management system. Prior to 1.11.38 and 2.0.0-RC.3, Chamilo LMS contains a Server-Side Request Forgery (SSRF) vulnerability in the Social Wall feature. The endpoint read_url_with_open_graph accepts a URL from the user via the social_wall_new_msg_main POST parameter and performs two server-side HTTP requests to that URL without validating whether the target is an internal or external resource. This allows an authenticated attacker to force the server to make arbitrary HTTP requests to internal services, scan internal ports, and access cloud instance metadata. This vulnerability is fixed in 1.11.38 and 2.0.0-RC.3.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-04-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-31941 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-31941?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-31941?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-31941 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
chamilo:chamilo_lmsbefore 1.11.38
chamilo:chamilo_lms2.0.0:alpha1
chamilo:chamilo_lms2.0.0:alpha2
chamilo:chamilo_lms2.0.0:alpha3
chamilo:chamilo_lms2.0.0:alpha4
chamilo:chamilo_lms2.0.0:alpha5
chamilo:chamilo_lms2.0.0:beta1
chamilo:chamilo_lms2.0.0:beta2
chamilo:chamilo_lms2.0.0:beta3
chamilo:chamilo_lms2.0.0:rc1
chamilo:chamilo_lms2.0.0:rc2

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON