dbcve.org
JspwikiApplication · Apache

CVE-2022-27166

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 XHRHtml2Markup.jsp could trigger an XSS vulnerability on Apache JSPWiki up to and including 2.11.2, which could allow the attacker to execute javascript in the victim's browser and get some sensitive information about the victim.

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 up to 2.11.2 contain a reflected XSS vulnerability in the XHRHtml2Markup.jsp endpoint. A carefully crafted request allows injection of arbitrary JavaScript that executes in the victim's browser, enabling session hijacking and sensitive information disclosure.

MitigationApply input validation and output encoding on the XHRHtml2Markup.jsp endpoint, or upgrade to JSPWiki version 2.11.3 or later which contains the security 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.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
    Locate the JSPWiki application in your environment by checking for JSPWiki WAR files, deployed applications, or the presence of the JSPWiki web application directory.
    Affected if JSPWiki is not found in the environment, the check is not applicable.
  2. Determine installed JSPWiki version
    Check the version of Apache JSPWiki by inspecting the application metadata (such as the version info in the WAR file, MANIFEST.MF, or the JSPWiki about page). Compare your version against the affected range.
    Affected if The installed version is any version prior to 2.11.3, including versions up to and including 2.11.2.
  3. Verify XHRHtml2Markup.jsp endpoint exists
    Confirm that the XHRHtml2Markup.jsp file is present in the deployed JSPWiki application, typically under the web application's JSP directory.
    Affected if The endpoint file exists and is accessible via HTTP/HTTPS.
  4. Test endpoint for XSS vulnerability
    If the endpoint is accessible, send a crafted request with a test XSS payload (such as a benign alert script) to the XHRHtml2Markup.jsp endpoint and observe if the payload is reflected unescaped in the response.
    Affected if The test payload is reflected in the response without proper HTML encoding, indicating the vulnerability is present.

The environment is affected if JSPWiki version is below 2.11.3 and the XHRHtml2Markup.jsp endpoint reflects unencoded input.

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

Apply input validation and output encoding on the XHRHtml2Markup.jsp endpoint, or upgrade to JSPWiki version 2.11.3 or later which contains the security fix.

Recommended fix High confidence

2.11.3

  1. Identify the currently running JSPWiki version by checking the administration interface or version file
  2. Review the JSPWiki 2.11.3 release notes and changelog for any migration requirements
  3. Create a complete backup of the JSPWiki installation including the WAR file, configuration files, and page data directory
  4. Stop the JSPWiki application server
  5. Download Apache JSPWiki version 2.11.3 from the official Apache JSPWiki distribution repository
  6. Deploy the new JSPWiki 2.11.3 WAR file to your application server
  7. Verify the application starts successfully and all plugins/extensions are functioning
  8. Test the XHRHtml2Markup.jsp endpoint to confirm the vulnerability is patched
Caveat Patch releases typically maintain backward compatibility; however, test all custom plugins and integrations before deploying to production

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

Fix this in Jspwiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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