Skip to main content

PILOS CVE-2026-71555

| EUVDEUVD-2026-54178 MEDIUM
Use of Web Link to Untrusted Target with window.opener Access (CWE-1022)
2026-08-06 security-advisories@github.com
4.1
CVSS 3.1 · Vendor: github
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Attacker plants malicious URL in PILOS meeting or file context
  2. Delivery
    Authenticated user clicks target="_blank" link
  3. Exploit
    Browser opens new tab with window.opener reference to PILOS tab
  4. Execution
    Malicious page calls window.opener.location.href to attacker-controlled phishing site
  5. Persist
    Original PILOS tab silently redirects
  6. Impact
    User submits credentials to attacker

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V3 - Web Frontend Security Window.opener access prevention
Exploitation Conditions

Exploitation requires three concurrent conditions: (1) the victim must be an authenticated PILOS user (PR:L per CVSS - unauthenticated exploitation is not possible); (2) the victim must actively click a link within PILOS that opens a new browser tab via target="_blank" (UI:R per CVSS - passive exploitation is not possible); and (3) the destination page must be attacker-controlled or attacker-influenced, meaning the attacker must be able to introduce a malicious URL into the user's PILOS context. Exploitation is limited by the requirement for authenticated user interaction, the need for the attacker to plant or influence a reachable URL within PILOS, and the progressive browser-side noopener defaults in Chrome 83+ and Firefox 79+ which reduce but do not eliminate the window.opener exposure. Versions 4.14.1 and later are not exploitable.

Impact

The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N scores 4.1 (Medium), which accurately reflects real-world risk. PR:L confirms that exploitation requires an authenticated victim, not an anonymous internet attacker. UI:R adds a meaningful barrier - the user must actively click a link. The Scope Change (S:C) captures the cross-origin browser boundary being crossed, distinguishing this from a purely internal impact. No EPSS score was provided in the input data, so exploitation probability cannot be quantified from that signal. The absence of a CISA KEV listing and any public POC indicates no confirmed mass exploitation. The primary threat model is targeted phishing of authenticated PILOS users - the attacker does not gain direct server-side access but can harvest credentials via a convincing fake login page. For most deployments, this is a patch-in-normal-cycle issue rather than an emergency. Note that modern browsers (Chrome 83+, Firefox 79+) have introduced implicit noopener behavior for some target="_blank" scenarios, which may independently reduce exploitability on updated client browsers, but relying on this is not a reliable mitigation.

Exploit ScenarioDerived

An attacker hosts a malicious page and introduces its URL into a PILOS session - for example, as a meeting link, shared room file reference, or external recording resource. An authenticated PILOS user clicks the link, which opens in a new browser tab; the malicious page immediately executes window.opener.location.href = 'https://pilos-phishing.attacker.com', redirecting the original authenticated PILOS tab to a convincing credential-harvesting login page. No public exploit code has been identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 06, 2026

Reverse tabnabbing in PILOS versions 2.1.0 through 4.14.1 exposes authenticated users to session hijacking via phishing by omitting the Cross-Origin-Opener-Policy (COOP) response header on pages that open links in new browser tabs. When an authenticated user clicks a target="_blank" link within PILOS, the newly opened page retains a live window.opener reference to the original PILOS tab, allowing the destination page to silently redirect that tab to an attacker-controlled site mimicking PILOS login. No public exploit has been identified at time of analysis, and the vendor-confirmed fix is available in v4.14.1.

RemediationAI

Upgrade PILOS to version 4.14.1, released at https://github.com/THM-Health/PILOS/releases/tag/v4.14.1, which resolves the missing COOP header via the refactored recording access controller in commit b50f2bd07c4f4a7d6a9981578238ae3579275d81. The security advisory is available at https://github.com/THM-Health/PILOS/security/advisories/GHSA-j4wr-p8gh-xrw5. If immediate upgrade is not feasible, configure the reverse proxy or web server (nginx or Apache) in front of PILOS to inject the response header Cross-Origin-Opener-Policy: same-origin on all responses; note this may break legitimate cross-origin pop-up flows if any are used by the deployment. A secondary compensating control is to add rel="noopener noreferrer" to all target="_blank" anchor elements in templates, though this requires application-level code changes and does not address root cause for dynamically opened windows.

Affected VersionsENISA

PILOS 2.1.0, < 4.14.1

Affected Packages

euvd pilos_2_1_0 fix: 4.14.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability maps to CWE-1022 (Use of Web Link to Untrusted Target with window.opener Access), a browser-level security boundary issue. PILOS is a Laravel/PHP-based web frontend for BigBlueButton, an open-source video conferencing platform deployed primarily in academic and healthcare settings. When a page opens a child tab via target="_blank" without either the rel="noopener noreferrer" anchor attribute or a Cross-Origin-Opener-Policy: same-origin response header, the browser preserves a cross-origin window.opener reference from the child tab back to the parent. The child can then call window.opener.location.href to navigate the parent tab to any URL. The patch in commit b50f2bd07c4f4a7d6a9981578238ae3579275d81 refactored recording format access from a direct API redirect to a server-rendered controller route (RecordingFormatController), enabling proper header injection and error handling in the new-tab context. Affected product scope covers PILOS 2.1.0 up to but not including 4.14.1, as confirmed by ENISA EUVD-2026-54178.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (github) PRIMARY 4.1 MEDIUM
AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N
vuln.today AI 4.1 MEDIUM

PR:L reflects that an authenticated victim is required; S:C captures the cross-origin browser boundary crossed via window.opener; UI:R is mandatory since the user must click the link.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (github).

CVSS VectorVendor: github

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
Required
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

Lifecycle Timeline

1
Patch available
Aug 06, 2026 - 23:03 EUVD

DescriptionCVE.org

PILOS (Platform for Interactive Live-Online Seminars) is a frontend for BigBlueButton. From 2.1.0 until 4.14.1, PILOS does not send a Cross-Origin-Opener-Policy response header, so pages opened by PILOS via a link that opens a new browsing context (e.g., target="_blank") retain a window.opener reference back to the originating PILOS tab. A malicious destination page reached this way can use window.opener to navigate or manipulate the original PILOS tab, a technique known as reverse tabnabbing, potentially redirecting an authenticated user to a phishing page that mimics PILOS. This issue is fixed in version 4.14.1.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Low
niche academic and healthcare BigBlueButton frontend, limited enterprise footprint
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

20
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +20
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy