dbcve.org
JspwikiApplication · Apache

CVE-2025-24854

MEDIUM · 6.1 CVSS v3.1 Published 2025-07-31
Fix available
A fix is available. Upgrade to 2.12.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 using the Image plugin could trigger an XSS vulnerability on Apache JSPWiki, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information about the victim. 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 · moderate confidence

An XSS vulnerability exists in Apache JSPWiki's Image plugin where a carefully crafted request can inject malicious JavaScript to execute in a victim's browser, potentially exposing sensitive session or user information.

MitigationUpgrade Apache JSPWiki to version 2.12.3 or later. If immediate patching is not feasible, temporarily disable or restrict the Image plugin until the upgrade can be completed.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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
    Locate the JSPWiki installation and check the version manifest, about page, or version file (commonly found in the WAR file, README, or admin interface)
    Affected if The installed version is lower than 2.12.3 (e.g., 2.12.2, 2.11.x, or earlier)
  2. Confirm Image plugin is deployed
    Verify that the Image plugin component is present in the JSPWiki installation (typically in the plugins or lib directory)
    Affected if The Image plugin is installed and accessible on the wiki instance
  3. Check if Image plugin is actively used
    Review wiki pages or configurations to determine if the Image plugin is being invoked in any page content or template
    Affected if The Image plugin syntax is used on any active wiki pages
  4. Assess exposure level
    Determine whether the wiki is accessible to untrusted users, external networks, or anonymous visitors
    Affected if The JSPWiki instance accepts requests from users who can supply image plugin parameters without trusted review

You are affected if your installed Apache JSPWiki version is below 2.12.3 AND the Image plugin is deployed and accessible to users who could inject malicious script parameters.

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 Apache JSPWiki to version 2.12.3 or later. If immediate patching is not feasible, temporarily disable or restrict the Image plugin until the upgrade can be completed.

Recommended fix High confidence

2.12.3

  1. 1. Back up your current JSPWiki installation and all wiki data before proceeding
  2. 2. Stop the JSPWiki service
  3. 3. Download Apache JSPWiki version 2.12.3 from the official Apache distribution repository (downloads.apache.org)
  4. 4. Extract the new version files
  5. 5. Replace the existing JSPWiki files with the new version 2.12.3 files, preserving your configuration and data directories
  6. 6. Verify file permissions are correctly set for the new installation
  7. 7. Restart the JSPWiki service
  8. 8. In a non-production environment first, verify the Image plugin works correctly and test that the XSS vulnerability is no longer present

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

Fix this in Jspwiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24854 — 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-24854 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