dbcve.org
JspwikiApplication · Apache

CVE-2022-24947

HIGH · 8.8 CVSS v3.1 Published 2022-02-25
Fix available
A fix is available. Upgrade to 2.11.2 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Apache JSPWiki user preferences form is vulnerable to CSRF attacks, which can lead to account takeover. 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

Apache JSPWiki user preferences form lacks anti-CSRF protection, allowing attackers to craft malicious requests that execute unwanted actions (such as changing user settings or passwords) when authenticated users visit attacker-controlled pages, potentially leading to full account takeover.

MitigationUpgrade Apache JSPWiki to version 2.11.2 or later to obtain the CSRF fix.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check Apache JSPWiki version
    Log in as administrator and navigate to the 'About' or 'System Information' page in the JSPWiki admin panel, or check the version manifest file in the JSPWiki installation directory (typically found in WEB-INF/lib or the build configuration)
    Affected if Installed version is any release prior to 2.11.2 (e.g., 2.11.1, 2.11.0, 2.10.x, etc.)
  2. Identify user preferences functionality
    Locate the UserPreferences or Profile page in JSPWiki where authenticated users can modify their account settings such as email, password, or display preferences
    Affected if The preferences form exists and is accessible to authenticated users without requiring explicit CSRF token submission
  3. Inspect preferences form for CSRF token
    Log in as a standard user, navigate to the user preferences settings page, view the page source (right-click > View Page Source), and examine the HTML form elements for a hidden input field containing a CSRF token, anti-CSRF token, or security token
    Affected if The preferences form lacks a hidden CSRF token field or the submitted form data does not include a validated token parameter
  4. Test form submission without token
    Using a browser developer tool or HTTP client, attempt to submit a preferences change request to the user preferences endpoint while omitting any CSRF token parameter to see if the request succeeds
    Affected if The request is processed successfully without requiring a valid CSRF token, indicating the anti-CSRF protection is missing or not enforced

A user is affected if their JSPWiki installation is version 2.11.1 or earlier AND the user preferences form can be submitted without providing a valid CSRF token.

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 obtain the CSRF fix.

Recommended fix High confidence

2.11.2 or later

  1. 1. Back up your current JSPWiki installation, including the wiki pages directory and database (if any).
  2. 2. Stop the JSPWiki service running on your server.
  3. 3. Download Apache JSPWiki version 2.11.2 or later from the official Apache repository (https://jspwiki.apache.org/).
  4. 4. Replace the existing JSPWiki installation files with the new version files, preserving your configuration and data directories.
  5. 5. Review and update any configuration files if required by the new version.
  6. 6. Start the JSPWiki service.
  7. 7. Verify the upgrade by logging in and checking that the user preferences form loads correctly.
  8. 8. Test that CSRF protection is working as expected in the new version.

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

Fix this in Jspwiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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