JspwikiApplication · Apache
CVE-2019-12404
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 InfoContent.jsp, 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 InfoContent.jsp. The vulnerability is triggered through specially crafted plugin link invocations, allowing attackers to inject malicious JavaScript that executes in victims' browsers, enabling session hijacking or sensitive data exfiltration.
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 the installed Apache JSPWiki versionCheck the version file, admin interface, or jar manifest for JSPWiki version informationAffected if The installed version is 2.10.5 or earlier, or any 2.11.0 milestone version (M1, M2, M3, M4)
-
Locate InfoContent.jsp in the deploymentSearch for InfoContent.jsp in the web application directory or WAR fileAffected if InfoContent.jsp exists and is accessible within the deployed application
-
Confirm plugin link functionality is accessibleVerify that the JSPWiki plugin system is enabled and plugin links can be invoked through the web interfaceAffected if Plugin invocation via URL parameters is possible and the InfoContent.jsp page processes these parameters
-
Test for reflected XSS in plugin link parametersSubmit a crafted plugin link request to InfoContent.jsp with a test script payload in the plugin parameter (e.g., ?plugin=<script>alert(1)</script>) and observe if the payload is reflected unescaped in the responseAffected if The malicious script payload is reflected and executed in the browser response without output encoding
You are affected if your JSPWiki version is 2.10.5 or earlier, or any 2.11.0.M1-M4 version, and InfoContent.jsp with plugin link functionality is accessible and reflects unsanitized input.
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 Apache JSPWiki to version 2.11.1 or later. If immediate patching is not possible, implement output encoding and input validation on InfoContent.jsp to neutralize script injection in plugin link parameters.
Fix this in Jspwiki
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12404 — 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-12404 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