JspwikiApplication · Apache
CVE-2019-10090
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 · uneditedOn 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 plain 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 confidenceApache JSPWiki versions up to 2.11.0.M4 contain a reflected XSS vulnerability in the plain editor component. Attackers can craft malicious plugin link invocations that, when processed, inject and execute arbitrary JavaScript in victim browsers, potentially exposing session tokens or other sensitive user data.
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
<= 2.10.5= 2.11.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify JSPWiki versionLocate the JSPWiki version information typically found in the about page, footer, or VERSION file in the installation directory. This may also be visible in the administration or system information page of the web interface.Affected if The installed version is 2.10.5 or lower, or exactly 2.11.0 (any milestone like M1-M4). Versions 2.11.1 and later are not affected.
-
Confirm plain editor is in useAccess the user preferences or editor settings within the JSPWiki interface. Check whether the plain editor mode is selected as the default or active editor for creating or editing pages.Affected if The plain editor is enabled or set as the active editor. This component contains the vulnerable code; users of other editors (like the WYSIWYG editor) are not affected by this specific flaw.
-
Verify plugin creation permissionsExamine the JSPWiki permission configuration or user role settings to determine whether users have the ability to create or invoke plugins. This is typically found in the security or permissions administration area.Affected if Users or groups have permission to create or invoke plugins, allowing them to craft malicious plugin link invocations that trigger the XSS payload.
-
Inspect HTTP request handlingIf you have access to logs or can test the application, examine how plugin link parameters are processed in HTTP requests to the edit or preview endpoints when using the plain editor.Affected if Plugin link parameters are reflected back into the response without proper sanitization, allowing injected script tags to execute in user browsers.
A user is affected if they run JSPWiki version 2.10.5 or lower, or version 2.11.0, with the plain editor enabled and plugin creation/invocation permissions granted to at least some users.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to Apache JSPWiki version 2.11.1 or later. As a temporary workaround, disable the plain editor or restrict plugin creation permissions until the upgrade can be applied.
Fix this in Jspwiki
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10090 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10090 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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