dbcve.org
JspwikiApplication · Apache

CVE-2019-10089

MEDIUM · 6.1 CVSS v3.1 Published 2019-09-23
Fix available
A fix is available. Upgrade to after 2.10.5 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
On Apache JSPWiki, up to version 2.11.0.M4, a carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki, related to the WYSIWYG editor, 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

Reflected XSS vulnerability in Apache JSPWiki's WYSIWYG editor where specially crafted plugin link invocations can inject malicious JavaScript into the rendered page, allowing attackers to execute scripts in victim browsers and access sensitive session information.

MitigationUpgrade to Apache JSPWiki version 2.11.0.M5 or later which contains the fix; alternatively, implement output encoding/sanitization on plugin link parameters in the WYSIWYG editor.

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.10.5= 2.11.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. Identify Apache JSPWiki installation version
    Access the JSPWiki 'About' page (typically /JSPWiki/About.jsp) or check the version file in the installation directory (version.properties or similar)
    Affected if The installed version is 2.10.5 or lower, or exactly 2.11.0
  2. Confirm the WYSIWYG editor is enabled
    Check JSPWiki configuration (jspwiki.properties or admin settings) for the editor configuration; verify users have WYSIWYG editor enabled in their preferences
    Affected if WYSIWYG editor is the default or available option for page editing
  3. Verify plugin links can be created
    Attempt to insert a plugin link through the WYSIWYG editor toolbar or examine if the wiki allows plugin invocation syntax like [{InsertPlugin plugin='...'}] in edited pages
    Affected if Plugin link insertion functionality is available and not explicitly disabled

You are affected if your JSPWiki version is 2.10.5 or lower, or exactly 2.11.0, and users have access to the WYSIWYG editor with plugin link insertion capability.

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.

From vendor data
Upgrade available Upgrade to a release after 2.10.5
Interim mitigation

Upgrade to Apache JSPWiki version 2.11.0.M5 or later which contains the fix; alternatively, implement output encoding/sanitization on plugin link parameters in the WYSIWYG editor.

Fix this in Jspwiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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