dbcve.org
JspwikiApplication · Apache

CVE-2022-24948

MEDIUM · 6.1 CVSS v3.1 Published 2022-02-25
Fix available
A fix is available. Upgrade to 2.11.2 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 user preferences for submission could trigger an XSS vulnerability on Apache JSPWiki, related to the user preferences screen, 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.11.2 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's user preferences screen allows attackers to inject malicious JavaScript through crafted user preference submissions, enabling execution in victim browsers and sensitive information disclosure.

MitigationUpgrade Apache JSPWiki to version 2.11.2 or later to remediate the XSS vulnerability.

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

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. Confirm JSPWiki installation exists
    Identify if Apache JSPWiki web application is deployed in your environment by checking for JSPWiki-related directories, WAR files, or running services on application servers (Tomcat, Jetty, etc.)
    Affected if JSPWiki is not present in the environment at all
  2. Determine installed JSPWiki version
    Access the JSPWiki version information page (typically at /JSPWiki/Edit.jsp?template=info or /JSPWiki/about.jsp) or check version files in the deployed application directory
    Affected if The installed version is any version prior to 2.11.2 (e.g., 2.11.1, 2.11.0, 2.10.x, etc.)
  3. Verify user preferences functionality is accessible
    Navigate to the user preferences or profile settings page in the JSPWiki interface (typically /JSPWiki/UserPreferences.jsp or similar) and confirm the form accepts user input
    Affected if User preferences screen is accessible and accepts submissions without sanitization validation
  4. Check for existing malicious preference entries
    Inspect stored user preference data in the JSPWiki backend (database or file-based storage) for any unexpected script tags, JavaScript event handlers, or iframe elements in preference fields
    Affected if Any user preference records contain unescaped HTML/Script content that could execute in a browser

You are affected if Apache JSPWiki is installed with a version lower than 2.11.2 and the user preferences feature is accessible, as this XSS vulnerability allows script injection through preference submissions.

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.11.2 or later
Fixed in 2.11.2
Interim mitigation

Upgrade Apache JSPWiki to version 2.11.2 or later to remediate the XSS vulnerability.

Recommended fix High confidence

2.11.2 or later

  1. 1. Back up the current JSPWiki installation, configuration files, and database/data directory
  2. 2. Stop the JSPWiki service
  3. 3. Download JSPWiki version 2.11.2 or later from the official Apache JSPWiki download location (e.g., https://tomcat.apache.org/jspwiki/)
  4. 4. Extract the new JSPWiki package
  5. 5. Replace the existing JSPWiki files with the new version, preserving custom configurations
  6. 6. Restore any custom plugins or extensions that were used in the previous installation
  7. 7. Start the JSPWiki service
  8. 8. Verify the installation by logging into the user preferences screen and confirming functionality
Caveat Review release notes for any configuration or compatibility changes between your current version and 2.11.2

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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