dbcve.org
JspwikiApplication · Apache

CVE-2022-28730

MEDIUM · 6.1 CVSS v3.1 Published 2022-08-04
Fix available
A fix is available. Upgrade to 2.11.3 or later.
See remediation →
68/100
Remediation priority · Elevated
High EPSS 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 on AJAXPreview.jsp 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. This vulnerability leverages CVE-2021-40369, where the Denounce plugin dangerously renders user-supplied URLs. Upon re-testing CVE-2021-40369, it appears that the patch was incomplete as it was still possible to insert malicious input via the Denounce plugin. Apache JSPWiki users should upgrade to 2.11.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's AJAXPreview.jsp. The vulnerability leverages an incomplete patch for CVE-2021-40369, where the Denounce plugin dangerously renders user-supplied URLs, allowing malicious input to execute JavaScript in victim's browser.

MitigationUpgrade Apache JSPWiki to version 2.11.3 or later to obtain the complete patch for the Denounce plugin input sanitization.

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
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 JAR file (jspwiki-main.jar or similar) in the webapp WEB-INF/lib directory, or check the version through the application's about/admin page. Common paths include /webapps/jspwiki/WEB-INF/lib/ or /var/lib/tomcat*/webapps/jspwiki/WEB-INF/lib/.
    Affected if The installed version is lower than 2.11.3 (e.g., 2.11.2, 2.11.1, 2.11.0, or earlier releases)
  2. Verify AJAXPreview.jsp is present
    Check for the presence of AJAXPreview.jsp in the JSPWiki web application root. Typical path: /webapps/jspwiki/AJAXPreview.jsp or check within the deployed WAR extraction.
    Affected if The file AJAXPreview.jsp exists and is accessible via the web server, indicating the vulnerable endpoint is available
  3. Confirm Denounce plugin is enabled
    Check JSPWiki's plugin configuration files (typically jspwiki.properties or plugin-related XML configs in WEB-INF/) to see if the Denounce plugin is loaded or available.
    Affected if The Denounce plugin is installed and active, allowing user-supplied content to be processed through the vulnerable code path

A user is affected if their Apache JSPWiki installation is version 2.11.2 or earlier and the Denounce plugin is enabled with AJAXPreview.jsp accessible.

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 Apache JSPWiki to version 2.11.3 or later to obtain the complete patch for the Denounce plugin input sanitization.

Recommended fix High confidence

JSPWiki 2.11.3 or later

  1. 1. Back up your current JSPWiki installation, including all configuration files and the database
  2. 2. Download JSPWiki version 2.11.3 (or the latest stable version) from the official Apache JSPWiki distribution repository
  3. 3. Stop the JSPWiki service
  4. 4. Replace the existing JSPWiki files with the new version files, preserving your configuration
  5. 5. Review the release notes for any specific migration or configuration requirements
  6. 6. Restart the JSPWiki service
  7. 7. Verify the fix by testing the AJAXPreview.jsp endpoint with the previously identified malicious input patterns
Caveat Review the 2.11.3 release notes for any specific migration requirements; minor patch releases typically maintain backward compatibility

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

Fix this in Jspwiki Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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