Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious opener_link URL with script payload
-
DeliveryLure logged-in backend media user into clicking
-
ExploitInject HTML/JS into media detail panel title
-
ExecutionRead CSRF token and submit template/module edit
-
ImpactAchieve code execution as administrator
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a logged-in REDAXO backend user who holds media permissions to click an attacker-crafted link to /redaxo/index.php?page=mediapool/media with a malicious opener_link value; the attacker needs no account. Two concrete conditions from the advisory must hold: opener_input_field must be ABSENT from the request (if present, the server overwrites opener_link with a safe link), and file_id must reference an existing media file (trivial, since IDs are sequential starting at 1). Delivery must be a top-level link click - click-less loading via <img> or <iframe> does NOT trigger it because the payload relies on a SameSite=Lax GET navigation. Escalation to code execution additionally requires the victim to be an administrator (for template/module edits); non-admin victims are limited to actions their role permits. The backend sends only Content-Security-Policy: frame-ancestors 'self', so no script CSP blocks the inline handler. |
| Impact | This is a genuine but conditional medium-severity issue rather than a drop-everything emergency, and the signals are internally consistent. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:A, base 5.1) correctly captures the core tension: the attacker needs no account of their own (PR:N), but exploitation is gated on active user interaction (UI:A) - specifically a logged-in REDAXO backend user with media permissions must click an attacker-supplied link. The vendor's own advisory confirms click-less delivery via <img>/<iframe> does NOT work because the payload fires on a top-level GET navigation (SameSite=Lax), so social engineering of a privileged user is a hard prerequisite. The subsequent-system impact (SC:L/SI:L) reflects the realistic worst case: the HttpOnly session cookie cannot be stolen, but the in-DOM CSRF token can, enabling authenticated actions bounded by the victim's role - escalating to effective code execution (template/module edits) only when the victim is an administrator. No EPSS score and no CISA KEV entry are present in the input, so there is no evidence of active or widespread exploitation; the vuln.today decision label is 'this_month,' not act_now/emergency. The RCE tag is real but contingent on admin victim interaction, so it should not be read as unauthenticated remote code execution. Net: patch on a normal priority cycle, prioritizing instances with many administrator accounts. |
| Exploit ScenarioDerived | An attacker emails or messages a REDAXO administrator a link that appears to point to the backend media pool but carries a crafted opener_link parameter containing a JavaScript payload. When the logged-in admin clicks it, the script executes in the backend origin, reads the CSRF token from the DOM, and silently submits a template or module edit that plants PHP, yielding code execution on the server. A working example payload URL is published in the GHSA advisory, though it is a demonstration string rather than packaged weaponized exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
REDAXO core releases before 5.21.3 render the backend media pool detail page's opener_link request parameter into the panel title as raw HTML, producing a reflected cross-site scripting condition (CWE-79/CWE-116) that an unauthenticated attacker can trigger by getting a logged-in backend user with media permissions to open a crafted link. The injected script executes in the backend origin with the victim's session; because the session cookie is HttpOnly it cannot be exfiltrated, but the CSRF token is present in the DOM, so the payload can perform authenticated actions limited to that user's role - escalating to code execution via template or module edits when the victim is an administrator. The advisory includes an illustrative payload URL; no separate public exploit release or confirmed in-the-wild exploitation was identified, and the priority signal places remediation in the this_month window rather than act-now.
RemediationAI
Vendor-released patch: REDAXO 5.21.3 - upgrade to this version, which removes the opener_link request parameter entirely rather than escaping it (REDAXO never generated the parameter itself and it required raw HTML by design, so escaping would not have preserved a working use case; the server-side select link built from opener_input_field is unaffected). If upgrading immediately is not possible, strip or block the opener_link query parameter on backend requests at the web server or reverse proxy level, which the advisory lists as the supported workaround. Adding a restrictive script Content-Security-Policy is worthwhile as defense in depth, but the vendor notes it is not a reliable standalone mitigation here because the backend currently ships only frame-ancestors 'self'. Review the advisory at https://github.com/redaxo/core/security/advisories/GHSA-5293-gg47-5xmh for the fix, and note that administrator accounts are the highest-value targets since template and module editing enables code execution from the injected script.
Affected VersionsENISA
Affected Packages
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 flaw sits in the media pool detail page of the REDAXO backend, where the opener_link request parameter was read directly from the request and concatenated into the panel title, which the template renders as raw HTML rather than escaped output. The neighbouring parameters in the same code section (info, warning, args[]) had been escaped by the earlier fix for CVE-2025-66026 (reflected XSS via args[types]), but opener_link was overlooked, so the same sink was left reachable. Two preconditions gate the sink: opener_input_field must be absent from the request (when present, the server overwrites opener_link with a safe, server-generated link), and file_id must reference an existing media file, which is trivial because media IDs are sequential starting at 1. Delivery must be a top-level GET navigation - the backend session cookie is SameSite=Lax, so a plain link click carries the session, while click-less vectors such as <img> or <iframe> do not work. The vulnerable code path was invisible to the project's Psalm taint analysis because the value crosses a compact()/extract() boundary when page context is handed to the subpage, breaking the taint trail. The backend emits only Content-Security-Policy: frame-ancestors 'self', so no script CSP blocked the injected inline event handler, and both variants of the detail page - write-permission edit mode and read-only mode - are affected.
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
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
Reflected XSS: attacker is unauthenticated (PR:N) but a privileged victim must click (UI:R); script executes in backend origin (S:C) with limited CSRF-token read and authenticated-action impact (C:L/I:L).
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
Lifecycle Timeline
1DescriptionCVE.org
REDAXO before 5.21.3 contains a reflected cross-site scripting vulnerability in the backend media pool detail page, where the opener_link parameter is rendered without HTML escaping. Unauthenticated attackers can lure logged-in backend users with media permissions into clicking a crafted link. The injected script can then read the CSRF token and perform actions with the victim's permissions, including code execution via template or module edits when the victim is an administrator.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
EUVD-2026-110800
GHSA-pmxw-f2gq-hx4c
NVD
CVE.org
EPSS
Exploit-DB