How severe is GHSA-7wj8-856p-qc9m?

GHSA-7wj8-856p-qc9m has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-7wj8-856p-qc9m?

GHSA-7wj8-856p-qc9m affects the following packages: redaxo/source (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-7wj8-856p-qc9m?

Update redaxo/source to 5.18.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7wj8-856p-qc9m is resolved across your whole dependency graph.

How do I detect GHSA-7wj8-856p-qc9m in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for redaxo/source. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-7wj8-856p-qc9m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-7wj8-856p-qc9m?

O3 pinpoints whether GHSA-7wj8-856p-qc9m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7wj8-856p-qc9m actively exploited in the wild?

No public exploit code has been indexed for GHSA-7wj8-856p-qc9m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-7wj8-856p-qc9m?

GHSA-7wj8-856p-qc9m has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 29th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-7wj8-856p-qc9m?

GHSA-7wj8-856p-qc9m is classified as Cross-site Scripting (XSS) (CWE-79), Code Injection (CWE-94). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-7wj8-856p-qc9m published, and has it been updated?

GHSA-7wj8-856p-qc9m was published on February 10, 2025 and was last updated on February 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-7wj8-856p-qc9m: Stored XSS in REDAXO (Medium 5.4)

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk29th percentile+0.24%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐘redaxo/source

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`redaxo/source`	≥ 5.12.0-beta1&&< 5.18.2	5.18.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for redaxo/source. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update redaxo/source to 5.18.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7wj8-856p-qc9m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-7wj8-856p-qc9m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7wj8-856p-qc9m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-7wj8-856p-qc9m in your dependencies?

O3 detects GHSA-7wj8-856p-qc9m across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-7wj8-856p-qc9m