Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.4

Stored XSS in REDAXO

CVE-2024-13209GHSA-7wj8-856p-qc9m

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (redaxo/source 5.18.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

  • Packagist redaxo/source

    Affected
    >= 5.12.0-beta1, <= 5.18.1
    Fixed in
    5.18.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS
  • CVE-2024-13209: 0.40% estimated exploitation activity in the next 30 days; percentile 34.31 (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 Stored XSS in REDAXO 5.18.1 - Article / "content/edit". Details On the latest version of Redaxo, v5.18.1, the article name field is susceptible to stored XSS. Impact A malicious actor can easily steal cookie using this stored XSS and perform a session hijacking attack.

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

    Published from ghsa record GHSA-7wj8-856p-qc9m

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-2024-13209

Advisory: Stored XSS in REDAXO
IDs: CVE-2024-13209, GHSA-7wj8-856p-qc9m
Record: https://patchnext.com/advisories/cve-2024-13209 (revision 1, source checked 26 Oct 2026, 14:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
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.18.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist redaxo/source: affected >= 5.12.0-beta1, <= 5.18.1; fixed in 5.18.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://github.com/advisories/GHSA-7wj8-856p-qc9m (GitHub-reviewed advisory GHSA-7wj8-856p-qc9m lists affected ranges: Packagist redaxo/source >=5.12.0-beta1 <=5.18.1)

Commands are suggestions: review each one before running it.

Loading voting…