dbcve.org
JspwikiApplication · Apache

CVE-2022-28732

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

Apache JSPWiki versions prior to 2.11.3 contain a stored XSS vulnerability in the WeblogPlugin component. By sending a specially crafted request, an attacker can inject malicious JavaScript that executes in victims' browsers, potentially exfiltrating session tokens, cookies, or other sensitive information.

MitigationUpgrade Apache JSPWiki to version 2.11.3 or later. Until the upgrade is applied, consider disabling the WeblogPlugin or implementing Content Security Policy (CSP) headers to mitigate XSS execution.

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 and version
    Locate the JSPWiki installation and check the version. Typically found in a version file, about page, or the war file name. Common locations include the /about.jsp page or the jspwikiWARName.properties file.
    Affected if The installed version is any release prior to 2.11.3 (e.g., 2.11.2, 2.11.1, 2.11.0, 2.10.x, etc.)
  2. Determine if WeblogPlugin is enabled
    Check the JSPWiki configuration files (jspwiki.properties or jspwiki.xml) for the WeblogPlugin module. Look for entries like 'WeblogPlugin' in the plugin configuration or the plugin's class name.
    Affected if WeblogPlugin is loaded and active in the JSPWiki configuration; the vulnerability only affects systems where this plugin is enabled.
  3. Inspect weblogs for suspicious content
    Access the WeblogPlugin functionality (typically at /weblog/ paths) and review recent blog entries and comments for unexpected HTML, script tags, or JavaScript payloads. Check the underlying data store or file system for blog content files.
    Affected if Any blog entries or comments contain unescaped HTML, script tags, or JavaScript code that was not authored by an administrator, indicating potential XSS injection.
  4. Review server logs for XSS attack patterns
    Examine JSPWiki server logs (catalina.out, jspwiki.log, or similar) for entries containing patterns like '<script>', 'javascript:', 'onerror=', 'onload=', or other typical XSS payloads submitted to WeblogPlugin endpoints.
    Affected if Logs show requests with XSS payloads directed at WeblogPlugin URLs, suggesting the vulnerability may have been exploited.

The environment is affected if the installed JSPWiki version is below 2.11.3 AND the WeblogPlugin component is enabled and accessible to 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 Apache JSPWiki to version 2.11.3 or later. Until the upgrade is applied, consider disabling the WeblogPlugin or implementing Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix High confidence

2.11.3 or later

  1. 1. Back up your existing JSPWiki installation, including the WAR file, configuration files (jspwiki.properties), and wiki data directory
  2. 2. Download Apache JSPWiki version 2.11.3 or later from the official Apache repository (https://jspwiki-wiki.apache.org/)
  3. 3. Stop the JSPWiki web application service
  4. 4. Replace the existing JSPWiki WAR file with the new version 2.11.3+
  5. 5. Restore your backed-up configuration files (jspwiki.properties) and wiki data to the new installation
  6. 6. Restart the JSPWiki web application service
  7. 7. Verify the upgrade was successful by logging in and confirming the WeblogPlugin functions correctly
Caveat Security patch release with minimal risk; standard upgrade procedure for Java web application

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

Fix this in Jspwiki Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
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,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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