JspwikiApplication · Apache
CVE-2019-12407
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 remember parameter on some of the JSPs, 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 stored XSS vulnerability in the 'remember' parameter of certain JSP pages. Attackers can craft malicious plugin link invocations containing JavaScript payloads that execute in victim browsers when the affected JSP pages are rendered.
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.
-
Determine Apache JSPWiki installation versionCheck the version file or startup logs for Apache JSPWiki. Common locations include version.properties in the WEB-INF directory, or check the application banner on startup. Look for a version identifier like 2.10.x or 2.11.0Affected if The installed version is 2.10.5 or earlier, or exactly 2.11.0 (not 2.11.0.M5 or later)
-
Identify JSP pages using the 'remember' parameterSearch the deployed JSP files for usage of the 'remember' parameter, typically in plugin invocation tags or form parameters. Examine JSP files in the /templates/ and /WEB-INF/ directories of the JSPWiki web applicationAffected if JSP pages containing the 'remember' parameter are present and accessible to users
-
Verify if plugin link invocation is enabledConfirm whether the plugin functionality is enabled in JSPWiki configuration. Check the jspwiki.properties file for plugin-related settings and verify the plugin finder is activeAffected if Plugin functionality is enabled and users can invoke plugin links containing the 'remember' parameter
-
Inspect user input handling for the 'remember' parameterExamine the JSP pages and underlying Java code that handle the 'remember' parameter. Look for whether input validation or output encoding is applied before renderingAffected if The 'remember' parameter value is reflected in HTML output without proper encoding or validation
A user is affected if they are running JSPWiki version 2.10.5 or earlier or exactly 2.11.0, and the plugin functionality with the 'remember' parameter is accessible and not sanitized before output.
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 which contains the fix. If immediate upgrade is not possible, implement strict input validation and output encoding on the 'remember' parameter across all affected JSPs.
Fix this in Jspwiki
Scoped from the published advisory
- Consultation3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12407 — 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-12407 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