Security readout for executives and security teams
Plain-English summary
PILOS versions before 4.10.0 allow an authenticated administrator to unintentionally end all active video conferences on a server by viewing crafted same-site content inside the application. This is disruptive but limited: it requires admin privileges and user interaction, and sources rate it low severity.
Executive priority
Treat as a scheduled remediation item, not an emergency. Prioritize upgrade where PILOS supports live classes, webinars, or operations where unexpected conference termination would disrupt service.
Technical view
The issue is a CSRF design flaw in a PILOS administrative API endpoint that terminates all active conferences. The endpoint uses HTTP GET for a destructive action. Authorization is enforced and cross-site triggering is reportedly blocked, but same-site embedded content rendered in the application can invoke it. Fixed in PILOS 4.10.0.
Likely exposure
Exposure is limited to organizations running THM-Health PILOS before 4.10.0, especially where administrators use the application while untrusted or user-supplied content may be rendered in same-site contexts.
Exploitation context
No active exploitation is reported in the provided sources, and the CVE is not listed as KEV. Abuse requires an authenticated administrator to view crafted content within the application, leading to availability impact only.
Researcher notes
The public description emphasizes a constrained CSRF: authorization exists and cross-site triggering is not possible. The weakness is destructive state change via GET reachable through same-site rendered content. Evidence supports low availability impact; no confidentiality or integrity impact is indicated.
Mitigation direction
- Upgrade PILOS to version 4.10.0 or later.
- Review vendor advisory and commit for exact remediation details.
- Restrict administrative access to trusted users.
- Avoid rendering untrusted content in administrative same-site contexts where possible.
Validation and detection
- Inventory PILOS deployments and identify versions below 4.10.0.
- Confirm whether administrators can access untrusted or user-controlled content inside PILOS.
- Review change management records for upgrade to 4.10.0 or later.
- Check application routes for destructive GET actions if maintaining custom forks.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-22800 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 2.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:L0.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
2.4LowVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/THM-Health/PILOS/security/advisories/GHSA-r24c-9p4j-rqw9CVE reference · x_refsource_CONFIRM
- https://github.com/THM-Health/PILOS/commit/d9ab9bb7ac0a8581c25e24cb7db2152d40be4d1bCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.