JspwikiApplication · Apache
CVE-2019-10078
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 · uneditedA carefully crafted plugin link invocation could trigger an XSS vulnerability on Apache JSPWiki 2.9.0 to 2.11.0.M3, which could lead to session hijacking. Initial reporting indicated ReferredPagesPlugin, but further analysis showed that multiple plugins were vulnerable.
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 2.9.0 through 2.11.0.M3 contain a stored XSS vulnerability in their plugin system. Attackers can craft malicious plugin links (initially found in ReferredPagesPlugin but affecting multiple plugins) that, when clicked by authenticated users, execute arbitrary JavaScript in the victim's browser, leading to session hijacking.
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.9.0, <= 2.11.0= 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.0/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 versionCheck your installed JSPWiki version. This is typically visible in the application footer, in the 'About' page, or by examining the JAR file metadata (jspwiki-core-x.x.x.jar). Compare this version number against the affected range of >= 2.9.0 and <= 2.11.0 (including 2.11.0.M3).Affected if The installed version falls within 2.9.0 through 2.11.0.M3 or equals 2.11.0.
-
Confirm plugin system is in useDetermine whether your JSPWiki instance has plugins enabled and whether users can create or edit content that invokes plugins. Check if plugins such as ReferredPagesPlugin, InsertPagePlugin, or other plugins are installed and active in your configuration.Affected if The plugin system is enabled and users can create or edit content containing plugin links.
-
Inspect stored content for plugin linksReview existing wiki pages, comments, and user-generated content for plugin markup in the format [{PluginName param=value}]. Specifically search for plugin invocations that accept user-controlled parameters.Affected if Stored content contains plugin links with unsanitized parameters that could contain malicious JavaScript payloads.
You are affected if your JSPWiki version is between 2.9.0 and 2.11.0 (inclusive of 2.11.0.M3 and 2.11.0) AND the plugin system is active with user-generated content present.
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 2.11.1 or later. As an interim measure, sanitize all plugin link parameters and implement strict input validation on user-supplied content before rendering.
Fix this in Jspwiki
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10078 — 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-10078 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