Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.8amended

REDAXO: Stored XSS in Mediapool Sync Page via Unescaped Filesystem Filenames

CVE-2026-63002GHSA-w998-qmw9-mf4m

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (redaxo/source 5.21.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.8 · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
EPSS
  • CVE-2026-63002: 0.20% estimated exploitation activity in the next 30 days; percentile 9.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The mediapool sync page (sync.php) renders filenames from the /media filesystem directory directly into HTML without applying rexescape() (i.e., htmlspecialchars). Any file placed in the media directory whose filename contains HTML metacharacters will execute JavaScript in the browser of any backend user who views the sync page. Details In redaxo/src/addons/mediapool/pages/sync.php, the variable $diffFiles is populated from actual filesystem filenames (files in /media/ not yet registered in the database). These filenames are then rendered without escaping: File: redaxo/src/addons/mediapool/pages/sync.php:119-120 File: redaxo/src/addons/mediapool/pages/sync.php:170 By contrast, all other filename displays in the codebase use rexescape($fname) (e.g., media.detail.php:236, media.list.php). The sync page is accessible to any backend user with the media[sync] permission (not exclusively admins). PoC 1. Place a file named <img src=x onerror=alert(document.cookie).txt into the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-w998-qmw9-mf4m

  2. Revision 1 · created ·

    Published from osv record GHSA-w998-qmw9-mf4m

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-63002

Advisory: REDAXO: Stored XSS in Mediapool Sync Page via Unescaped Filesystem Filenames
IDs: CVE-2026-63002, GHSA-w998-qmw9-mf4m
Record: https://patchnext.com/advisories/cve-2026-63002 (revision 2, source checked 26 Oct 2026, 14:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: redaxo/source 5.21.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist redaxo/source: affected <= 5.21.1; fixed in 5.21.2

## Suggested inspection (read-only)
- Packagist redaxo/source: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on redaxo/source.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-w998-qmw9-mf4m (OSV record GHSA-w998-qmw9-mf4m lists affected ranges: Packagist redaxo/source >=0 <5.21.2 (fixed))
- Verified: https://github.com/advisories/GHSA-w998-qmw9-mf4m (GitHub-reviewed advisory GHSA-w998-qmw9-mf4m lists affected ranges: Packagist redaxo/source >=0 <=5.21.1)

Commands are suggestions: review each one before running it.

Loading voting…