dbcve.org
JspwikiApplication · Apache

CVE-2022-46907

MEDIUM · 6.1 CVSS v3.1 Published 2023-05-25
Fix available
A fix is available. Upgrade to 2.12.0 or later.
See remediation →
68/100
Remediation priority · Elevated
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 several JSPWiki plugins 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.12.0 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.12.0 contain reflected XSS vulnerabilities in multiple JSPWiki plugins. Attackers can craft malicious requests containing JavaScript payloads that execute in victim browsers when they interact with vulnerable plugin endpoints, enabling session hijacking, credential theft, or sensitive data exfiltration.

MitigationUpgrade Apache JSPWiki to version 2.12.0 or later to obtain patched plugin components. If immediate upgrade is not feasible, disable or restrict access to vulnerable plugin endpoints as a temporary mitigation.

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

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. Determine installed JSPWiki version
    Locate the JSPWiki version by checking the administrative interface, a VERSION file in the installation directory, or the pom.xml/build configuration if source is available. Compare the version number against the affected range (anything below 2.12.0).
    Affected if Installed version is below 2.12.0
  2. Identify active JSPWiki plugins
    Access the JSPWiki administration panel or plugin management section to list all installed and enabled plugins. Review the plugin configuration files in the WEB-INF or plugins directory if accessible.
    Affected if Any plugin endpoints are enabled and accessible to users
  3. Test plugin endpoints for XSS vulnerability
    With appropriate authorization, submit crafted requests containing script tags or HTML payloads to plugin endpoints (e.g., plugins that accept user input via query parameters or form fields). Observe whether the input is reflected back without proper encoding in the response.
    Affected if User-supplied input is reflected unescaped in plugin responses
  4. Review access controls on plugin endpoints
    Examine the JSPWiki security configuration and web.xml to determine which plugin endpoints are exposed to unauthenticated or low-privileged users versus restricted to administrators.
    Affected if Vulnerable plugin endpoints are accessible to non-admin users

A user is affected if their JSPWiki installation is version 2.12.0 or lower AND vulnerable plugin endpoints are enabled and accessible to at least some 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.12.0 or later
Fixed in 2.12.0
Interim mitigation

Upgrade Apache JSPWiki to version 2.12.0 or later to obtain patched plugin components. If immediate upgrade is not feasible, disable or restrict access to vulnerable plugin endpoints as a temporary mitigation.

Recommended fix High confidence

2.12.0

  1. 1. Back up your current JSPWiki installation including the wiki pages and configuration files
  2. 2. Download Apache JSPWiki version 2.12.0 from the official Apache distribution repository (https://jspwiki.apache.org/)
  3. 3. Stop the JSPWiki service running on your server
  4. 4. Replace the existing JSPWiki files with the new version 2.12.0 files, preserving your configuration and page data directories
  5. 5. Verify that all plugins are compatible with version 2.12.0
  6. 6. Restart the JSPWiki service
  7. 7. Test that the application functions correctly and the XSS vulnerability is resolved

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
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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