dbcve.org
JspwikiApplication · Apache

CVE-2025-24853

HIGH · 7.5 CVSS v3.1 Published 2025-07-31
Fix available
A fix is available. Upgrade to 2.12.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-Site Scripting (XSS) vulnerability in Apache JSPWiki allows attackers to inject malicious JavaScript via wiki markup or markdown syntax when creating header links. This enables execution of arbitrary JavaScript in victim browsers to steal sensitive session or user information.

MitigationUpgrade to Apache JSPWiki version 2.12.3 or later which patches the XSS vulnerability in both the wiki markup and markdown parsers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JspwikiApplication
Affected:< 2.12.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify JSPWiki installation version
    Check the JSPWiki version from the application's About page, startup logs, or version manifest file typically found in the WEB-INF directory
    Affected if The installed version is anything less than 2.12.3 (e.g., 2.12.2, 2.11.x, earlier versions)
  2. Determine if wiki markup parsing is enabled
    Inspect the JSPWiki configuration file (jspwiki.properties or jspwiki.xml) for the wiki.text.provider or similar setting that enables wiki markup rendering
    Affected if Wiki markup parsing is enabled and users can create or edit pages with header link syntax
  3. Determine if markdown parsing is enabled
    Check the JSPWiki configuration for markdown plugin or provider settings (e.g., markdown provider, MarkdownRenderer)
    Affected if Markdown parsing is enabled and users can create or edit pages with header link syntax
  4. Verify user content creation capability
    Review whether the application allows authenticated or anonymous users to create or edit wiki pages containing header links
    Affected if Users have the ability to insert custom header links using wiki markup ([{header}] or markdown (# header) syntax

You are affected if running any Apache JSPWiki version below 2.12.3 AND the wiki markup or markdown parser is enabled, allowing users to create content with header links.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.12.3 or later
Fixed in 2.12.3
Interim mitigation

Upgrade to Apache JSPWiki version 2.12.3 or later which patches the XSS vulnerability in both the wiki markup and markdown parsers.

Recommended fix High confidence

2.12.3

  1. Back up your current JSPWiki installation and database/data files before upgrading
  2. Download Apache JSPWiki version 2.12.3 or later from the official Apache JSPWiki distribution repository
  3. Stop the running JSPWiki service
  4. Replace the existing JSPWiki JAR files and application files with the new version 2.12.3
  5. Review and apply any configuration changes required for the new version
  6. Start the JSPWiki service
  7. Test that wiki markup and markdown parsing work correctly and that the XSS vulnerability is mitigated
  8. Deploy the upgrade to production after validating in a staging environment
Caveat Review the release notes for 2.12.3 to check for any configuration or compatibility changes from your current version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jspwiki Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,010
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24853 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24853 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data