How severe is GHSA-rrff-chj9-w4c7?

No CVSS score has been assigned to GHSA-rrff-chj9-w4c7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rrff-chj9-w4c7?

GHSA-rrff-chj9-w4c7 affects the following packages: org.apache.jspwiki:jspwiki-main (Maven), org.apache.jspwiki:jspwiki-markdown (Maven). Ecosystems affected: Maven.

How do I fix GHSA-rrff-chj9-w4c7?

Update org.apache.jspwiki:jspwiki-main to 2.12.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rrff-chj9-w4c7 is resolved across your whole dependency graph.

How do I detect GHSA-rrff-chj9-w4c7 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.jspwiki:jspwiki-main. 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-rrff-chj9-w4c7 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-rrff-chj9-w4c7?

O3 pinpoints whether GHSA-rrff-chj9-w4c7 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-rrff-chj9-w4c7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rrff-chj9-w4c7 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 type of vulnerability is GHSA-rrff-chj9-w4c7?

GHSA-rrff-chj9-w4c7 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type 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-rrff-chj9-w4c7 published, and has it been updated?

GHSA-rrff-chj9-w4c7 was published on July 31, 2025 and was last updated on November 5, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-rrff-chj9-w4c7

Fix: apache/jspwiki#376

GHSA-rrff-chj9-w4c7 is a Cross-site Scripting (XSS) vulnerability in org.apache.jspwiki:jspwiki-main. O3 Security confirms whether GHSA-rrff-chj9-w4c7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Apache JSPWiki Cross-Site Scripting (XSS) Vulnerability via Header Link Rendering

Also known asCVE-2025-24853

Published

Jul 31, 2025

Updated

Nov 5, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 5, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

☕org.apache.jspwiki:jspwiki-main☕org.apache.jspwiki:jspwiki-markdown

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

Description

Further research by the JSPWiki team showed that the markdown parser allowed this kind of attack too.

Apache JSPWiki users should upgrade to 2.12.3 or later.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.jspwiki:jspwiki-main`	all versions	2.12.3
☕Maven	`org.apache.jspwiki:jspwiki-markdown`	all versions	2.12.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.jspwiki:jspwiki-main. 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 org.apache.jspwiki:jspwiki-main to 2.12.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rrff-chj9-w4c7 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-rrff-chj9-w4c7 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-rrff-chj9-w4c7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A carefully crafted request when creating a header link using the wiki markup syntax, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information about the victim. Further research by the JSPWiki team showed that the markdown parser allowed this kind of attack too. Apache JSPWiki users should upgrade to 2.12.3 or later.

O3 Security · Impact-Aware SCA

Is GHSA-rrff-chj9-w4c7 in your dependencies?

O3 detects GHSA-rrff-chj9-w4c7 across Maven 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