dbcve.org
JspwikiApplication · Apache

CVE-2022-34158

HIGH · 8.8 CVSS v3.1 Published 2022-08-04
Fix available
A fix is available. Upgrade to 2.11.3 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
A carefully crafted invocation on the Image plugin could trigger an CSRF vulnerability on Apache JSPWiki before 2.11.3, which could allow a group privilege escalation of the attacker's account. Further examination of this issue established that it could also be used to modify the email associated with the attacked account, and then a reset password request from the login page.

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

A CSRF vulnerability in the Image plugin of Apache JSPWiki before 2.11.3 allows attackers to perform actions on behalf of authenticated users, including escalating group privileges, modifying account email addresses, and triggering password reset requests.

MitigationUpgrade to Apache JSPWiki 2.11.3 or later. Additionally, implement CSRF tokens for state-changing operations in the Image plugin and verify other plugins for similar vulnerabilities.

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.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
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. Identify JSPWiki installation
    Look for JSPWiki application files, typically deployed in a web container (Tomcat, Jetty, etc.). Check for the presence of jspwiki.jar or the jspwiki web application directory.
    Affected if JSPWiki is installed and accessible on the server
  2. Determine installed JSPWiki version
    Check the jspwiki.jar file version in the web application WEB-INF/lib directory, or look for a version file in the JSPWiki installation. Alternatively, access the JSPWiki welcome page which often displays the version number.
    Affected if The version displayed is below 2.11.3 (for example, 2.11.2, 2.11.1, 2.10.x, etc.)
  3. Check if Image plugin is in use
    Review JSPWiki pages for usage of the Image plugin syntax, typically [[{Image url=...}]] or similar Image plugin markup. Check the WEB-INF/lib directory for jspwiki-plugin.jar or bundled plugin jars.
    Affected if The Image plugin is deployed and enabled in the JSPWiki installation

A user is affected if Apache JSPWiki version is below 2.11.3 and the Image plugin is enabled and accessible to authenticated users.

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.3 or later
Fixed in 2.11.3
Interim mitigation

Upgrade to Apache JSPWiki 2.11.3 or later. Additionally, implement CSRF tokens for state-changing operations in the Image plugin and verify other plugins for similar vulnerabilities.

Recommended fix High confidence

JSPWiki 2.11.3 or later

  1. Backup your current JSPWiki installation and database
  2. Stop the JSPWiki application server
  3. Download JSPWiki version 2.11.3 or later from the official Apache JSPWiki distribution site (https://jspwiki-wiki.apache.org/)
  4. Replace existing JSPWiki files with the new version files
  5. Migrate configuration files to ensure compatibility with the new version
  6. Start the JSPWiki application server
  7. Verify the installation and confirm the Image plugin functions correctly

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

Fix this in Jspwiki Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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