JspwikiApplication · Apache
CVE-2019-10087
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 Page Revision History, 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 · moderate confidenceApache JSPWiki versions up to 2.11.0.M4 contain a reflected XSS vulnerability in the Page Revision History feature. The vulnerability is triggered when a specially crafted plugin link is invoked, allowing attackers to inject malicious JavaScript that executes in victims' browsers.
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 installed JSPWiki versionCheck the JSPWiki administration page or the 'About' page in the web interface for the version number. Alternatively, inspect the JSPWiki JAR file properties or the pom.xml if the source is deployed.Affected if The version is 2.10.5 or lower, or exactly 2.11.0 (including 2.11.0.M1 through 2.11.0.M4)
-
Confirm Page Revision History is accessibleNavigate to any wiki page, locate the 'Page History' or 'Revision History' option in the page menu, and verify the feature loads successfully.Affected if The revision history feature is enabled and users can access it
-
Verify plugin system is enabledCheck the JSPWiki configuration file (jspwiki.properties) for the presence and enabled status of the plugin configuration, or attempt to invoke a known plugin via URL in the revision history context.Affected if The plugin system is enabled and plugins can be invoked within the revision history view
-
Test for reflected XSS in revision history plugin linksIf you have access to testing, craft a plugin link URL with a malicious script payload in the revision history view (e.g., ?plugin=SomePlugin¶m=<script>alert(1)</script>) and observe if the script executes or is reflected unencoded in the response.Affected if The injected script content is reflected in the HTML response without proper encoding or validation
A user is affected if their JSPWiki version is 2.10.5 or lower, or exactly 2.11.0 (including milestone versions up to 2.11.0.M4), and the Page Revision History feature with plugin invocation is accessible to 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.0.M5 or later. As an interim measure, implement output encoding and input validation on plugin link parameters within the revision history component.
Fix this in Jspwiki
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10087 — 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-10087 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